Signed, offline-verifiable contract-change authorization. Only a granted change can proceed.
| Endpoint | https://app.coderifts.com/mcp (streamable-http) |
|---|---|
| Registry version | 1.0.3 |
| Now | 3 tools · grade D (51) · pin ts_d5fcdad8d482e469867f607120815474 · protocol 2025-06-18 |
| First / last listed | 2026-10-27 03:52 UTC / 2026-10-27 03:52 UTC |
| Grade over time | 2026-10-27: D (51), 3 tools |
Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.
Tools: preflight_change_set verify_receipt get_decision_details
preflight_change_set | Use this when: a contract artifact (OpenAPI, GraphQL, protobuf, AsyncAPI, MCP manifests, or agent tool schemas) changes before merge, deploy, publish, or tool registration; AND any agent-executed operation with no supported contract type — send type agent_operation. Do not call for documentation-only changes, static readiness scoring, or receipt verification. Use analyze for risk only; authorize r params: artifacts, context, previous_receipt, execution_grant_request, response_detail, idempotency_key, preflight_mode*, decision_spec_version, derivation |
verify_receipt | Verify a CodeRifts signed chain-receipt you ALREADY HOLD: cryptographic
authenticity (signature + key id), body binding, and — when lifecycle indices
are available — whether it is currently valid authorization (not expired,
superseded, or revoked) for a stated operation/target.
Use this when:
- You already obtained a chain_receipt / receipt token from a prior preflight
(or CI artifact) and are params: token*, operation, target_id, environment, fingerprint, audience, repository, branch, pull_request, base, head, decision_result |
get_decision_details | Retrieve a PAST CodeRifts decision by exactly one identifier
(case_id | decision_id | fingerprint): full report, breaking changes, scores,
and linked receipt metadata if stored.
Use this when:
- You have a decision_id (or fingerprint) from a previous preflight, PR
comment, or CI log and need to inspect or explain that past decision.
- You are auditing why a prior ALLOW/WARN/BLOCK was issued.
- params: case_id, decision_id, fingerprint |
Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.