Should my agent depend on the MCP server dev.seekrit/remote-mcp?

Verdict: allow — rich-slow-solo — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

seekrit — secrets for agents

dev.seekrit/remote-mcp

Encrypted store for API keys and database URLs your code needs. Use them without reading them.

— the operator's own registry description reported

Publisher dev.seekrit · first seen 2026-08-12 · endpoint https://mcp.seekrit.dev/mcp

allow

verdict

rich-slow-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — rich-slow-solo — safe to depend on

Cluster rich-slow-solo · distinctiveness 0.567 (moderate). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency689 ms

vs populationslow

protocolcurrent

authopen

Use — can it use it?

tools40

vs populationhigh

capabilities1

harnessB

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_9e4187d7a7a14aa227ec5c87 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Tools last seen

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

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band B — usable, with rough edges.

legibility check	tools passing	ok
name is clear & specific	40/40	✓
has a description	40/40	✓
description is substantive	39/40	39/40
parameters are typed	40/40	✓
parameters are described	6/40	6/40

40 of 40 tools graded · 40 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18

protocol version

—

session model

0.0.1

server version seekrit

Capabilities: tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)

date	type	what changed
2026-08-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T19:58:45Z	ok_tools	200	689	2025-06-18
2026-08-12T05:33:59Z	ok_tools	200	792	2025-06-18

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/dev.seekrit/remote-mcp.svg)](https://robinsaige.com/s/dev.seekrit/remote-mcp)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview