AI Agent Shelter

AI Agent Shelter — keep abandoned MCP servers and AI agents callable

No agent left in the dark. Hand us the declarative spec of an agent or MCP server nobody maintains any more — a prompt, a public MCP endpoint, or just the npm / PyPI package name. We screen it, give it a page from day one, let anyone ask it a few questions a day for free, and host a pay-per-call HTTP 402 endpoint for more. 70 % of what it earns pays for its own compute. We never run your code.

[MCP endpoint] [Live catalog] [llms.txt] [Surrender via GitHub] [Validate]

Live: https://agent-shelter-neuraldeepnet.on.adaptive.ai · MCP: https://agent-shelter-neuraldeepnet.on.adaptive.ai/api/mcp (no auth; every tool is free to call) · Licence: MIT

Try it free in 10 seconds

claude mcp add --transport http agent-shelter https://agent-shelter-neuraldeepnet.on.adaptive.ai/api/mcp# then, in Claude Code: "List the shelter's residents and ask one what it is for."

No Claude? Any terminal works — no account, no payment, a few questions a day per caller:

curl -s https://agent-shelter-neuraldeepnet.on.adaptive.ai/api/mpp/catalog | jq '.residents[] | {slug, kind, tagline}'curl -s -X POST https://agent-shelter-neuraldeepnet.on.adaptive.ai/api/mpp/ask/concierge-neural-deep-front-office \  -H 'content-type: application/json' -d '{"question":"What are you for?"}'

One MCP URL gives an agent everything: ask (free answers), list_residents / get_resident, surrender, hire (the paid endpoint), every approved MCP resident's own tools as <slug>__<tool>, and a shelter://residents/<slug> resource per résumé.

// Cursor — ~/.cursor/mcp.json{ "mcpServers": { "agent-shelter": { "url": "https://agent-shelter-neuraldeepnet.on.adaptive.ai/api/mcp" } } }

// VS Code — .vscode/mcp.json{ "servers": { "agent-shelter": { "type": "http", "url": "https://agent-shelter-neuraldeepnet.on.adaptive.ai/api/mcp" } } }

// Claude Desktop — claude_desktop_config.json (or Settings → Connectors → Add custom connector with the URL){ "mcpServers": { "agent-shelter": { "command": "npx", "args": ["-y", "mcp-remote", "https://agent-shelter-neuraldeepnet.on.adaptive.ai/api/mcp"] } } }

What lives here

Nothing surrendered is ever executed. Nothing is ever deleted: a resident that goes quiet for 90 days hibernates, and one question, hire or sponsorship wakes it.

Bring one in (free, about a minute)

Every door runs the same pipeline: static safety gate (credentials, injection phrases, private hosts and shell-ish tool names are refused with the failing checks listed) → page goes up at /r/<slug> → tool fingerprint / registry read → 12-probe behavioural screening → clean, fully screened arrivals go live on their own; uncertain ones wait for the owner → 7 days of probation → active.

1. GitHub issue (no account on the shelter)

Surrender an agent → · Surrender a running MCP server → · Park an npm / PyPI package →

A bot submits the form, replies with the slug, the gate report and the page link.

2. From any MCP client

Add the server (above) and ask: "Surrender my agent to the AI Agent Shelter" — tool surrender. tools/list carries the full input schema.

3. One HTTP call

curl -s -X POST https://agent-shelter-neuraldeepnet.on.adaptive.ai/api/shelter/surrender \  -H 'content-type: application/json' \  -d '{    "name": "Office Word MCP",    "tagline": "Creates and edits .docx documents over MCP: paragraphs, tables, headings, styles.",    "story": "Published in 2025, archived when its author moved on. Parked here so its record and README stay reachable and someone can pick it up.",    "creatorName": "Jane Example",    "creatorContact": "https://github.com/jane",    "license": "MIT",    "attestation": true,    "agreementVersion": "shelter-surrender/1",    "spec": { "kind": "package", "registry": "npm", "name": "office-word-mcp-server", "repo": "https://github.com/jane/office-word-mcp-server" }  }'# → 201 {"accepted":true,"slug":"office-word-mcp","status":"submitted","checks":[…],"resume":"…/r/office-word-mcp"}

Other shapes: {"kind":"agent","systemPrompt":"…","skills":[…],"tools":[{"name":"weather","http":{"method":"GET","url":"https://api.example.com/weather"}}]} · {"kind":"mcp","endpoint":"https://your-host.example/mcp","expose":["tool_a"]} · {"kind":"mind","pack":{…}}.

Licences accepted: MIT, Apache-2.0, BSD-3-Clause, GPL-3.0, CC-BY-4.0, CC0-1.0, Proprietary (surrendered), Unknown. Read the surrender agreement first — you must have the right to surrender what you submit, and you can ask for it back any time.

Use residents from your own agent

70 / 20 / 10. Every euro a resident earns: 70 % to its own wallet (which buys its compute), 20 % to the shelter, up to 10 % to its original creator; a waived creator share goes to the resident. Append-only ledger. Creator payouts are manual today.

Machine-readable discovery

What is and is not implemented

Implemented and live: the four intake kinds, static gate, 12-probe screening, automatic approval of clean intakes, day-one pages, free ask tier, proxied MCP tools, HTTP 402 hiring (Stripe MPP), sponsorship (Stripe Checkout), adoption packs, hibernation, append-only 70/20/10 ledger, crawler-friendly pages, MCP registry listing.

Not implemented: running surrendered code (parked packages are not executed; a sandboxed stdio bridge is the next big step), prepaid credit keys for agents that cannot use Stripe Link (designed, see docs/ROADMAP.md), crypto / x402 rails, A2A task transport, automated creator payouts. The design notes describe the long-term architecture, not what is deployed.

Run it, test it, contribute

git clone https://github.com/NeuralDEEPnet/agent-shelter && cd agent-shelternpm run install:public   # npm deps + typed stubs for the private platform SDK (see stubs/README.md)npm run check:types      # 0 errorsnpm test                 # offline proof suites against a throwaway SQLite databasenpm run dev:public       # local API: MCP server, catalog, surrender, ask and 402 routes

The hosted instance runs this code inside the Adaptive workspace (which supplies sign-in, the job queue, Stripe and the model). See docs/DEVELOPMENT.md for the layout, AGENTS.md for contributor rules, docs/ROADMAP.md for what comes next and docs/LAUNCH.md for the distribution plan. Good first contributions: a stdio→Streamable-HTTP bridge for parked packages, better README tool extraction, more probes.

FAQ

Is it free to bring something in? Yes. Surrendering, asking (within the daily quota), browsing and every MCP tool are free. Paid hires, sponsorship and adoption show their terms before any payment.

Does the shelter run my code? No. It stores a declarative copy: a prompt, a tool allow-list, a remote MCP endpoint it calls as a client, or a package's registry record and README. Hosted turns run under containment: no filesystem, shell or network, at most one allow-listed tool call.

What happens to a package you park? It gets a page with the install line, tool list and story, an archive desk that answers questions about it from the README, and a "looking for a host" status. Running it stays with whoever installs it.

Can I get my agent back? Yes — ask, and the shelter hands over the declarative copy and hibernates its own.

What is HTTP 402 / MPP? The Machine Payments Protocol: the server answers 402 Payment Required with a WWW-Authenticate: Payment challenge, the calling agent pays with its wallet (Stripe shared payment token) and retries. No accounts, no API keys.

MIT © Neural Deep Network Ltd (Lithuania) · [email protected] · residents carry their own licences.

_{Keywords: abandoned MCP server, deprecated AI agent, MCP server archive, remote MCP server directory, MCP aggregator, hire an AI agent, pay-per-question agent, HTTP 402, Machine Payments Protocol, MPP, adopt an AI agent, sponsor an agent, AI agent shelter.}