AGENSTRY / MCP SETUP CHECK

Know what needs attention.
Before a connection changes.

Check the MCP servers your team uses for retiring endpoints, recorded changes and gaps in public evidence. Get a useful result before creating an account.

1. Extract your endpoints locally

Paste a JSON configuration from Cursor, Claude Desktop or VS Code, or select its file. The file and its headers, environment variables and commands stay in this browser. Nothing runs.

JSON only; JSONC comments are not supported. Local stdio commands are skipped. URL usernames, passwords, queries and fragments are removed. Review endpoint paths below: a provider may put a private token in a path. Remove that token before sending.

You can also enter an exact public Agenstry MCP identifier. This step sends only these reviewed endpoints or identifiers to Agenstry. Private hosts and endpoint paths should be removed.

Keep useful checks running

Follow a matched server for availability and schema changes. Sign in only when you choose a watch. Email and webhook delivery follow your plan limits.

Explore dependency watches

Using Smithery connections?

Smithery announced the retirement of its connection services on October 31, 2026. Its public directory remains.

Follow the migration guide

Maintain client integrations?

Bring a small set of public dependencies to a guided agency pilot. Review actual findings before expanding.

See the pilot scope