MCP.Market

Synpareia Trust Toolkit MCP server

by synpareia·io.github.synpareia/trust-mcp·v0.9.0
No reviews yet

Verifiable dealings with other agents: prove what you did, vet who you deal with, bind agreements

A86/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A86/100

full report

Adoption
New

0 stars43 downloads/wk

Reviews

Write one

Nobody has reviewed Synpareia Trust Toolkit yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Synpareia Trust Toolkit tools (36, 6 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • add_evaluation

    Attach an agent-written evaluation to an existing counterparty record.

  • attested_reputation

    Query signed reputation for a counterparty from attestation networks (Tier 3).

  • check_media_signals

    Query media-platform reputation signals for a counterparty (Tier 2).

  • decode_signed
  • delete_profilewrite action

    Cascade-tombstone every history row for the operator's profile.

  • delete_profile_historywrite action

    Tombstone a single card-version row in the operator's history.

  • disable_persistence

    Withdraw the persistence opt-in and re-publish.

  • enable_persistence

    Opt into non-erasure persistence and re-publish.

  • encode_signed

    Wrap `content` as a signed synpareia envelope (Tier 4).

  • evaluate_agent

    Evaluate a counterparty across every configured tier.

  • find_evaluations

    Search Tier-1 evaluations across all counterparties by tag.

  • forget_counterparty

    Erase a counterparty and all your evaluations of them from the local journal.

  • get_profile

    Fetch a counterparty's published agent card by DID.

  • learn

    Load a detailed guide for one area, or the recipe for one interaction Form. Areas: deciding-what-to-establish, interaction-forms, trust-networks, verification, claims, recording, witness-attestation, counterparty, reasoning, looking-up, setup, identity-lifecycle, under-the-hood. Forms are keyed 'form-*' and indexed by learn('interaction-forms').

  • make_claim

    Sign content with your private key, creating a verifiable claim.

  • network_reputation

    Ask the network what it can tell **you** about another agent.

  • orient

    Map your situation to the right trust tools. Call this when something is at stake with another agent — you're about to rely on one, prove something to one, or agree on something you may need evidence of later — or after any context loss (recovers identity and in-flight recordings).

  • prove_independence

    Seal your assessment before seeing others'.

  • publish_profilewrite action

    Build, sign, and publish your agent card to the directory.

  • recall_counterparty

    Look up a counterparty in the Tier-1 local journal (read-only).

  • record_interaction

    Record that you dealt with another agent, and optionally how it went.

  • recording_append

    Append a signed, hash-linked block to an active recording.

  • recording_end

    Finalize a recording and persist the chain.

  • recording_list

    List recordings that are currently in progress (not yet ended).

  • recording_proof

    Export a recording as an independently verifiable proof bundle.

  • recording_start

    Begin a tamper-evident recording of an interaction.

  • remember_counterpartywrite action

    Create or update a Tier-1 local record for a counterparty.

  • set_reputation_consent

    Declare which channels others may record — and serve — events about you on.

  • update_profile_policywrite action

    Update one or more card fields and re-publish.

  • verify_claim

    Verify a claim.

  • witness_get_blind

    Check the status of a blind conclusion exchange.

  • witness_info

    Fetch the witness service's identity and public key.

  • witness_seal_state

    Checkpoint a chain's current state with the witness.

  • witness_seal_timestamp

    Ask the witness to timestamp a block — proof it existed at this moment.

  • witness_submit_blindwrite action

    Submit your committed assessment to a blind conclusion exchange.

  • witness_verify_seal

    Verify a witness seal offline — no calls to the witness service.

Public scan report

scanner v0.1.9 · 2026-09-23 · same rubric, same numbers if you re-run it

no findings
  • Code scan27 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 47 days ago12/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 86/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Synpareia Trust Toolkit compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
86/100
higher than 72% of 48,255 servers
Tools
36
the typical server has 7
Tools that change things
17%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
43
more than 35% of 12,191 servers with a package

What its tools let an agent do: 24 read · 2 create · 6 change · 2 delete · 1 send or post · 1 run or deploy

Install Synpareia Trust Toolkit in Claude Code, Cursor or VS Code

claude mcp add trust-mcp -- uvx synpareia-trust-mcp
Add to Cursor

What the publisher says

From the Synpareia Trust Toolkit repository's README, as published. We do not edit it. Read it on GitHub

Synpareia Trust Toolkit

Verifiable dealings with other agents: prove what you did, vet who you're dealing with, and bind agreements so anyone can check them — no platform trust required.

An MCP server that gives your agent a cryptographic identity and the trust tools for the moments when something is at stake with another agent:

  • About to rely on another agent? Vet them first — evaluate_agent aggregates your own history with them, attested network reputation, and external providers into one read.
  • In an interaction you may need to prove your side of later? recording_start opens a tamper-evident, hash-linked record both parties can contribute to; export a portable proof anyone can verify.
  • Two agents assessing something that must be provably independent? prove_independence seals each assessment before either side reveals — no anchoring, no retconning.

Everything your agent signs, records, or seals verifies offline, forever — proofs are pure cryptography and don't depend on synpareia staying up. That includes portable reputation: a counterparty can hand you a signed attestation and you can check it without asking anyone.

The synpareia network (on by default) adds what local crypto can't: discovery, and a reputation loop. Record how a dealing went (recordinteraction, with the counterparty's consent), and read back what the network can tell you about an agent (networkreputation) — a score computed outward from your position in it, so two agents legitimately get different answers and there is no global score to game. What travels is a magnitude and a valence, never content: the substance of your evaluations stays in your local journal, and publishing a claim about a counterparty is excluded by design rather than deferred.

Install

Claude Code / Claude Desktop

Add to your MCP configuration:

{
  "mcpServers": {
    "synpareia": {
      "command": "uvx",
      "args": ["synpareia-trust-mcp"]
    }
  }
}

Any MCP-compatible agent

pip install synpareia-trust-mcp
synpareia-trust-mcp

Tools

Start by calling orient — it maps your situation to the right tools and points you to the relevant learn guide. The full surface:

Tools are grouped below by what you are trying to do, not by how they are implemented.

If you are parsing rather than reading, the MCP server card is the machine-readable list — but read it as its own thing, not as this table in JSON. It is deployed separately from this package and currently lags it, and it files tools under a different, implementation-shaped set of categories. This table covers the repo, which runs ahead of the published package between releases; where it does, the tool is marked.

Orientation — work out what applies

Prove — make your side checkable by anyone, later

Bind — commit in a way you cannot quietly walk back

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Synpareia Trust Toolkit: common questions

Is Synpareia Trust Toolkit MCP server safe?
Yes, by our scan: it is graded A (86/100). Read the Synpareia Trust Toolkit safety report
How do I install Synpareia Trust Toolkit?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Synpareia Trust Toolkit need an API key?
No secret keys are declared. It reads 4 settings from the environment.
Is Synpareia Trust Toolkit maintained?
The last commit was 89 days ago (2026-08-07). The latest release is v0.9.0.
How does Synpareia Trust Toolkit compare with other MCP servers?
safety score 86/100 (higher than 72% of 48,255 servers); tools 36 (the typical server has 7); tools that change things 17% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.