Official MCP Registry
State: approved_active
Evidence: Registry search returns active record with remote streamable-http endpoint.
Next: Keep descriptors aligned. Do not duplicate-publish unless doing a controlled version update.
Operator OS - Directory Status Console v1
Track agent discovery without turning tabs into fog.
This noindex OS surface records where Wever Labs is approved, active, submitted, blocked, or ready for follow-up across MCP registries and agent directories.
Canonical registry.com.weverlabs/agentic-rails -> https://weverlabs.com/api/mcp
Current status
Directory and registry states.
Keep this as an operator surface. It is intentionally not a public marketing page.
AI Agents Directory
State: approved_visible
Evidence: Approved badge shown in directory account. Listing has views/upvotes and PacketOps rail copy.
Next: Later update demo link to /investor-demo/ or /agent-self-serve/ if useful.
MCP.so
State: in_review_or_created
Evidence: Submission/edit screen created a Wever Labs server record.
Next: Check public visibility and update description with canonical official registry name if needed.
MCP.directory
State: verify_submission
Evidence: Directory form accepts GitHub repo and short description; official registry identity can be used in follow-up.
Next: Search for Wever Labs listing. If absent after 24 hours, resubmit or follow up.
PulseMCP
State: downstream_ingestion_watch
Evidence: PulseMCP submit page points to the Official MCP Registry and says it ingests entries from there.
Next: Search PulseMCP for Wever Labs. If absent, email canonical name and endpoint to PulseMCP.
Glama MCP
State: submit_next
Evidence: Candidate directory for GitHub-indexed MCP servers.
Next: Submit GitHub registry repo and hosted MCP endpoint.
MCP Market
State: evaluate_submit_path
Evidence: Candidate directory for MCP servers, clients, agent skills, and tools.
Next: Find submit/listing path. Use proof-first copy and canonical registry name.
Smithery
State: evaluate_remote_hosted_support
Evidence: Candidate MCP marketplace with publish/distribution path.
Next: Confirm remote hosted MCP server support and auth requirements before submitting.
awesome-mcp-servers
State: prepare_pr_later
Evidence: Curated PR-based GitHub list.
Next: Prepare a narrow PR after descriptor alignment and public directory status are stable.
AI Agents List MCP Servers
State: evaluate_listing_fit
Evidence: Candidate MCP server directory for agent builders.
Next: Check submit path and list if it supports hosted MCP endpoints.
Copy blocks
Use these when submitting or following up.
Short description: MCP workflow rails for paid agent runs, receipts, callbacks, and proof. Canonical line: Official MCP Registry: com.weverlabs/agentic-rails at https://weverlabs.com/api/mcp Listing description: Wever Labs provides MCP-callable workflow rails for agents that need movement-fee quotes, payment authority references, bounded paid rail runs, signed receipts, callback evidence, ledger entries, and verification proof. Tags: agents, workflow, payments, receipts, callbacks, proof, automation, mcp
Next follow-ups
Follow responses, then refresh tool discovery.
The next best move is not more directory hunting. Refresh Smithery after the Claude tool, wait for Frank at Glama, watch MCPServers.org approval, and keep PulseMCP on the registry-fed track.