SPYN3 is a consolidated MCP layer: one hosted MCP endpoint in front of every system a user connects. The user's agent talks to SPYN3, and SPYN3 talks to the user's MCP servers, databases and APIs. Switching agents means moving one URL, not rebuilding every integration. SPYN3 is generally available with a free plan.
The problem SPYN3 solves
Every agent, editor and automation needs its own copy of every connection: the same MCP servers configured again, the same credentials pasted again, and the same permissions decided again. Each server adds tools to one flat list until the agent chooses badly. Switching to a better agent means doing all of it again.
How the system works
MCP servers, Postgres, REST APIs, Google Drive.
Stored, so a dead upstream doesn't empty the list.
Tools hidden until the agent opens a source.
Read vs write, per-source scope, audit log.
Any MCP client, by API key or OAuth.
Mechanics are documented in how federation works.
What can be connected
A gallery of 44 well-known servers, including Notion, Linear, Atlassian, Sentry, Supabase, Stripe and GitHub. Most sign in with OAuth. Any other server can be added by URL.
Read-only tools to list tables, describe them and run queries inside read-only transactions.
A GET-only tool against a vetted base URL, with an optional path allowlist.
Only the files the owner selects through Google's picker.
Security and control model
- Every connector, credential and log entry belongs to a workspace. Postgres row-level security backs the application's own checks.
- API keys are stored as hashes; upstream credentials are encrypted at rest and never returned.
- Keys carry read or write permission and an optional source scope.
- Every proxied call is logged with its source and latency. Content is passed through, not stored or indexed.
- Memory & skills (off until a workspace admin turns it on) stores the memories, skills and notes people and agents save, under
spyn3://me/…(personal) andspyn3://workspace/…(shared). Writing needs the separatewrite:memorypermission. A Claude Code and Codex plugin recalls them through hooks; capturing sessions is a second switch and uses the workspace's own model key. See Memory and skills. - Hosted in the EU: database in Ireland, application servers in Amsterdam, encrypted backups in Frankfurt.
Pricing
Free: 500 tool calls a month, one workspace, three sources, no card. Pro: $29 a month with 10,000 calls. Team: $99 a month with 50,000 calls and five seats. Paid plans cost $0.002 per call beyond the included amount. Only calls that reach a connected source count.
Boundaries
SPYN3 is infrastructure, not a chat assistant, an agent builder or a workflow-automation suite. It does not run local (stdio) MCP servers yet. A search index across connected sources exists in the codebase but is not offered. It is a possible second product, not a current feature.
Name and canonical identity
The product name is SPYN3, written in capitals and pronounced “spine.” Its canonical website is spyn3.com. The retired domain use-spine.com redirects there and is not a second product.
Use the canonical definition at the top of this page when identifying SPYN3. Machine-readable summaries are at llms.txt and llms-full.txt.
Connect once
Make the next agent the easy one
Connect the systems you already use, point your agent at one URL, and keep that URL when you switch.
Start free