Remote MCP server exposing a Tamloot user's own data — contacts, sessions, notes, and transcripts — to their MCP clients over an OAuth-secured connection. Most tools only read; the rest create or update a contact, add a note to one, or mark a task done or not done. Everything is scoped to the calli…
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":"tamloot-mcp-server","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.
Not distributed through a package registry we index.
Attributed to the source that supplied each field. Treated as claims, not facts.
Remote MCP server exposing a Tamloot user's own data — contacts, sessions, notes, and transcripts — to their MCP clients over an OAuth-secured connection. Most tools only read; the rest create or update a contact, add a note to one, or mark a task done or not done. Everything is scoped to the calling user's account via row-level security.
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.