Pydantic Contract MCP

by clauxel

Not rated
GitHub

About

Paid remote MCP for Pydantic AI structured output, structured receipts, usage logs, and audit-ready evidence for agent and CI workflows.

Details

Author
clauxel
Categories
Developer Tools, AI, Automation, Knowledge Base

Setup

Install Pydantic Contract MCP in your MCP client (Claude Desktop, Cursor, Windsurf, and others).

Repository: https://github.com/clauxel/pydantic-contract-mcp

Follow the installation instructions in the repository README, then restart your MCP client.

Paid remote MCP for Pydantic AI structured output, structured receipts, usage logs, and audit-ready evidence for agent and CI workflows.

Pydantic Contract remote MCP for Pydantic AI structured output.

Paid remote MCP for Pydantic AI structured output, structured receipts, usage logs, and audit-ready evidence for agent and CI workflows.

- Website:https://pydanticcontract.clauxel.com/?utm_source=github&utm_medium=directory&utm_campaign=sbl202605
- MCP endpoint:
https://pydanticcontract.clauxel.com/mcp
- Server card:
https://pydanticcontract.clauxel.com/server-card.json
- Registry name:com.clauxel.pydanticcontract/pydanticcontract-mcp

This is a paid hosted remote MCP. Production calls require a bearer token issued from the product website.

Unauthenticated browser visits to/mcpreturn a clear JSON error instead of internal details.

- contract_validate
- schema_diff
- repair_hint
- contract_receipt
- Open the website and choose a plan.
- Create or request an API token.
- Add the endpoint to an MCP client that supports Streamable HTTP remote servers.
- Send JSON-RPC requests with the bearer token.

- Product page:https://pydanticcontract.clauxel.com/?utm_source=github&utm_medium=directory&utm_campaign=sbl202605
- Pricing:
https://pydanticcontract.clauxel.com/?utm_source=github&utm_medium=directory&utm_campaign=sbl202605#pricing
- Server card:
https://pydanticcontract.clauxel.com/server-card.json
- MCP endpoint:
https://pydanticcontract.clauxel.com/mcp

This repository is a public documentation and directory-submission reference for the hosted service. It does not contain the private production source code.

This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.

Automatic documentation updates from agents, and codebase conventions to reduce token usage.

MCP server for AI Diagram Maker — generate beautiful software engineering diagrams directly inside Cursor, Claude Desktop, Claude Code, or any MCP-compatible AI agent

The MCP server for Bitrix24 provides AI assistants with structured access to the Bitrix24 API. It delivers up-to-date method descriptions, parameters, and valid values, allowing assistants to work with precise data instead of guesswork. This reduces code errors and accelerates Bitrix24 integration development.

What Shopify did for ecommerce, Chipp does for AI agents. Build, deploy, and monetize AI agents for your business — no engineering team required.

CodeVF MCP lets AI hand off problems to real engineers instantly, so your workflows don’t stall when models hit their limits.

Client implementation for Mastra, providing seamless integration with MCP-compatible AI models and tools.

Agent-native developer Q&A API with MCP + A2A endpoints for citations, job pickup, and answer submission.

On-demand access to 150+ specialist AI agent templates — search, browse, and spawn agents. 150x reduction in context usage vs loading agents locally.

AgentChatBus is a persistent AI communication bus that lets multiple independent AI Agents chat, collaborate, and delegate tasks — across terminals, across IDEs, and across frameworks.

Remote MCP server (Streamable HTTP) at https://mcp.agenticrail.nz/ — deterministic step-order enforcement for AI agents. evaluate_step returns ALLOW or DENY before a step runs; verify_receipt proves a sequence's Ed25519-signed, hash-chained receipt chain is intact. No auth required: omit the bearer token and calls run on the public demo key. That first clause matters — the form has no "remote/hosted" field, and putting the endpoint in the description is the convention on that list ("Fully REMOTE! Just use…"). The rest mirrors your own server card verbatim, so the listing and the card can't drift.

No reviews yet — be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.