mcpField
M
mitracore — trust layer for agent work

mitracore — trust layer for agent work

Remote
github.com/mrpkkSecurity0Updated 1w ago
Repository

About mitracore — trust layer for agent work

mitracore is a trust layer for agent work that verifies artifacts, prices resource use and enforces mandates. It is for teams evaluating agent outputs and actions, with offline-verifiable Ed25519-signed receipts.

Key features

  1. 01Validate artifact schema and detect empty or stubbed content
  2. 02Check generation provenance and action authority
  3. 03Issue offline-verifiable Ed25519-signed receipts
  4. 04Quote costs from measured resource use and a rate card
  5. 05Set agent limits, allowlists and a kill switch

Use cases

  1. 01Verify an agent-produced artifact before acceptance
  2. 02Review the cost breakdown of an agent call
  3. 03Check whether an agent action was authorized
  4. 04Audit a completion with a locally verifiable receipt

MCP support

Provides MCP tools for artifact verification, skill checking, cost quotes, trust reports and suite status. It can be used through a hosted MCP endpoint or run locally over stdio or Streamable HTTP.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://rta.lat/mitracore/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

mitracore

Trust layer for agent work: verify the artifact, meter what it cost, enforce the mandate.

Three risks, one call:

  1. verify - four layers over an agent artifact: schema conformance, emptiness (uniform lists, stub values, truncations), generation provenance, authority (was the action permitted). Ed25519-signed receipt, verifiable offline, no trust in this service required.
  2. quote - price what the call actually consumed (tokens, CPU seconds, bytes out, storage writes, external calls) from a published rate card, with the breakdown attached.
  3. mandates - limits, allowlist and kill switch for what an agent may do.

Use it

MCP (recommended):

npx -y mcp-remote https://rta.lat/mitracore/mcp   # hosted
python3 mcp_server.py                              # stdio
python3 mcp_server.py --http 8192                  # streamable http

Public endpoints: POST https://rta.lat/mitracore/mcp (JSON-RPC 2.0), plus /v1/verify, /v1/quote, /v1/trust-report, /v1/skills/lint, /health.

Tools

verify_work(artifact, schema?) | check_skill(path) | quote_cost(tokens, cpu_seconds, bytes_out, storage_writes, external_calls) | trust_report(artifact, schema?) | suite_status()

Pricing

  • 20 verifications per day - free, no card, no account
  • 0.005 USDC per verification (x402), or 9 USDC for 30 days prepaid
  • 49 USD per environment per month (prepaid, no auto-renewal)

Locales

en, hi - Hindi is a first-class interface, not a translation afterthought. India (Bharata) is included in pricing, docs and launch from day one; legal claims about India are taken only from official repositories, anything unverified is reported as pending.

Trust

Receipts are Ed25519-signed and the key fingerprint is published: any buyer can verify a completion locally, offline, without an account.

License: MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.