Model Context Protocol tool calling support for Pydantic AI
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":"pydantic-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.
# pydantic-mcp  [Model Context Protocol](https://modelcontextprotocol.io) tool calling support for [Pydantic AI](https://ai.pydantic.dev/). Just create an `mcp.ClientSession` and call `tools = await mcptools(session)` to get a list of `pydantic_ai.Tool` instances for the supported tools. Example: https://github.com/rectalogic/pydantic-mcp/blob/98c4e9abf31837cb48ebeb3eae6cb55b16c841e8/tests/demo.py#L15-L25 ## Demo You can run the demo against [Groq](https://groq.com/) `llama-3.1-8b-instant`: ```sh-session $ export GROQ_API_KEY=xxx $ uv run tests/demo.py "Read and summarize the file ./LICENSE" Secure MCP Filesystem Server running on stdio Allowed directories: [ '/users/aw/projects/rectalogic/pydantic-mcp' ] The file ./LICENSE is a MIT License agreement. It states that the software is provided "as is" without warranty and that the authors and copyright holders are not liable for any claims, damages, or other liability arising from the software or its use. ```
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.