Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"docketeer-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# docketeer-mcp MCP (Model Context Protocol) server support for [Docketeer](https://github.com/chrisguidry/docketeer). Connects the agent to any MCP-compatible server so new capabilities are config, not code. ## Tools | Tool | Purpose | |------|---------| | `list_mcp_servers` | Show configured and connected servers | | `connect_mcp_server` | Connect to a configured server | | `mcp_oauth_complete` | Complete an OAuth flow for a server | | `disconnect_mcp_server` | Disconnect from a server | | `search_mcp_tools` | Semantic search across MCP server tools | | `use_mcp_tool` | Call a tool on a connected server | | `add_mcp_server` | Save a new server configuration | | `remove_mcp_server` | Delete a server configuration | ## Configuration Server configs live in `$DOCKETEER_DATA_DIR/mcp/` as individual JSON files. ### Stdio server ```json { "command": "uvx", "args": ["mcp-server-time"], "env": {"TZ": "America/New_York"}, "networkAccess": false } ``` ### HTTP server ```json { "url": "https://weather-api.example.com/mcp", "headers": {"Authorization": "Bearer ..."} } ``` Secrets stay in the data directory, outside the agent-visible workspace.
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.