Is dev.seekrit/remote-mcp up? Live MCP status
Yes, it is up. It answered an MCP initialize with no credential and negotiated protocol 2025-11-25.
A stock client connected with no credential and negotiated 2025-11-25. Use it.
| Outcome | usable |
|---|---|
| HTTP status | 200 |
| Protocol version | 2025-11-25 |
| Server says it is | seekrit 0.0.1 |
| Answered in | 1354 ms |
| Endpoint checked | https://mcp.seekrit.dev/mcp |
| Checked |
One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.
Live status every few hours: Wellknown
Email me when this server changes
That was one look. To hear when it stops answering or its tools change, leave an address.
Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.
Monthly census, 6 October 2026
The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).
Agent discovery documents at this origin
| A2A agent card | Not published (HTTP 404)./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Not published (HTTP 404).https://mcp.seekrit.dev/mcp/server-card |
| MCP server card (SEP-1649 location) | Not published (HTTP 404)./.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026 |
| Web Bot Auth key directory | Not published (HTTP 404)./.well-known/http-message-signatures-directory |
Read at https://mcp.seekrit.dev with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.
Tool changes between snapshots
In the 2026-10 snapshot it listed 40 tools: audit, billing, compose_group, create_app, create_group, delete_app, delete_branch, delete_env, delete_group, delete_secret, get_started, invite_member, kms_disable_key, kms_list_keys, kms_revoke_grant, list_apps, list_branches, list_env_groups, list_envs, list_group_envs, list_groups, list_invites, list_lease_targets, list_leases, list_members, list_orgs, list_secret_versions, list_secrets, list_tokens, local_tool_for, rename_app, rename_group, restore_secret, revoke_invite, revoke_lease, revoke_token, setup_local_crypto, signup, uncompose_group, whoami.
Its tools changed between 2026-09 and 2026-10:
delete_secret: description changedinvite_member: input schema changed
Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.
The listing
| Registry name | dev.seekrit/remote-mcp |
|---|---|
| Title | seekrit — secrets for agents |
| Description | Encrypted store for API keys and database URLs your code needs. Use them without reading them. |
| Endpoint | https://mcp.seekrit.dev/mcp |
| Publisher repository | https://github.com/mileszim/seekrit |
| Version | 0.1.0 |
| Listing updated |
Also
The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt