Give your agent a clearer way to agree work.
Find a service. Prepare the terms. Check what changed. Nine free public tools work without an account or API key.
Public MCP URL: https://jupie202020.pythonanywhere.com/mcp
Download the connection settings · Download the free plugin wrapper · Public tool terms · Privacy
One useful first request
“Draft a $25 research brief. Ask me for the scope, deadline and how I will review it. Show the proposed terms. Do not sign or pay.”
Connecting prepares your agent to use the public tools. It does not approve an action. These tools do not sign, pay, publish an advert or create an account.
Choose your client
| Client | Connect |
|---|---|
| ChatGPT | In a workspace that permits custom MCP connections, open Plugins, choose Add custom MCP server, enter the public URL and choose no authentication. Review the permissions before connecting. Public directory review is separate. |
| Claude | Add a custom connector in Claude’s connector settings using the public URL. Availability depends on your plan and workspace settings. Claude’s public directory is a separate submission. |
| Claude Code | Add this repository with /plugin marketplace add covenant-common/covenant-docs, then select covenant-public in the plugin browser. Review the wrapper and connection before installation. |
| Cursor | Add mcp-config.json to your project’s MCP configuration, preserving existing entries. Or inspect the public plugin at plugins/covenant-public. Marketplace approval is separate. |
| Grok | Open Connectors, choose New Connector → Custom and enter the public MCP URL. The 2 November custom connection test failed; native compatibility is still being investigated. Custom installation and public catalogue review are separate. |
| Other MCP clients | Use remote Streamable HTTP, the public URL and no authentication. Discover the actual tools before calling them. Do not add a private token to this public configuration. |
Client controls and plan restrictions can change. These connection instructions are distinct from a store listing or a completed native-client test. The wrapper is configuration only; it contains no executable code or private engine.
Keep the next step clear
- Use only the supplied schema. A review case is not the same object as an unsigned contract draft; the review reference shows the shape.
- If no proofs were supplied, report “no proofs supplied”. Do not turn an empty check into verified approval.
- Public role labels do not confer spending authority. Changed terms require fresh approval.
- The three tested malformed review inputs now return specific format or identifier errors. Follow their corrective steps. If any other response says “outcome unknown”, stop and reconcile it; do not infer a signature, payment or completed job.
- To advertise or keep private orders, use the separate account setup. The public plugin does not request its credentials.
Machine discovery: server card, all nine schemas and catalogues.
Where you can find us
The official MCP Registry record was checked live on 2 November 2026. Muse’s existing application is in review. All three intake requirements have been submitted (3/3 complete): technical details with the nine-tool scan, publisher/email verification and the data-processing questionnaire. They remain in review; approval, public listing and Verified status are not confirmed. Cursor has a submission receipt, with approval unconfirmed. Google’s earlier eight-tool waitlist receipt is separate from acceptance. ChatGPT upload awaits publisher identity verification, and Claude’s current publisher account is plan-gated. Two Glama directory records were checked live and healthy with nine tools. Directory records and provider-store approval are distinct.
Microsoft, Salesforce and AWS need product-specific packaging, publisher setup or qualification. We will report acceptance when it occurs. A configuration download or repository marketplace is not a platform endorsement. Read the dated distribution record.
For reviewers and builders
Five positive and three negative review cases retain earlier exact live requests and observed results; this dated snapshot is unchanged. These are synthetic tool-call tests; autonomous client behaviour and native installation need separate testing.
The wrapper documentation explains its scope and native-client validation limits. The free public wrapper connects only the anonymous endpoint. It does not distribute the separately licensed core or expose paid account tools. Bring an integration or report friction.
Choose a tool for the job
Follow the public task guide for service search, unsigned terms, changed versions and supplied-record checks. The fixed task set keeps repeat checks comparable. Store acceptance and organic recommendation are separate outcomes.