Proofable MCP

io.github.proofablePublished by GitHub account proofablev0.1.10Updated Nov 7, 2026

Context and control for any AI. Agent identity, scoped access, and proof across tools.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring AI & ML

Server details

Identifier: io.github.proofable/mcp
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account proofable for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.proofable%2Fmcp.svg)](https://sourceweft.com/mcp/io.github.proofable%2Fmcp?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Remote Proofable endpoint that lets an assistant check, create and reuse verification proofs and manage agent identity and permissions for a signed-in profile.

What you can do: Load the signed-in profile, proof index, agents and permissions
List supported verification checks and their required inputs
Check whether a wallet already holds qualifying proofs, or reuse one and get the next step
Create a proof, or prepare and submit a check that needs another signer
Search and read proofs, including bodies and comments
Update proof metadata or visibility, vote and comment; check, create and mount agents
When to use it: Useful when an assistant must confirm eligibility or access against existing proofs, reuse a current proof instead of re-verifying, or act under a scoped agent identity with defined permissions.
Requirements: A remote MCP endpoint added to the client; no local package. Sign-in via the hosted flow or the setup command is needed for most tools; four tools run signed out. Servers and automation can use an access key stored as PROOFABLE_ACCESS_KEY and sent as a Bearer token.

Before you install

Tools can create proofs, change proof visibility (private revokes public access), post votes and comments, and create agents; proofs stay offchain unless publishing to a hub is explicitly requested. Access keys are secrets and should not be pasted into chat or committed to code. Sign-in is required for private context and proof bodies.

Installation

In SourceWeft

Open Proofable MCP in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.proofable%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "proofable": {
      "type": "http",
      "url": "https://mcp.proofable.me/mcp"
    }
  }
}

README

Proofable MCP

[npm] [License]

The trust harness for AI. Identity and governance for the agents you run, in every MCP client.

Connect Proofable once, and your agents can use your profile, proofs, permissions, and protected tools in Cursor, Claude, Codex, VS Code, ChatGPT, and any other MCP client.

Start

Open Set up Proofable, choose your client, and finish sign-in. Then ask:

For a specific requirement:

text

Check whether I already have the proof needed for this task. Reuse it if it qualifies; otherwise show me the next step.

Check whether I already have the proof needed for this task. Reuse it if it qualifies; otherwise show me the next step.

Connect

[Add to Cursor] [Install in VS Code]

Add https://mcp.proofable.me/mcp to any MCP client, or use a standard MCP configuration:

json

{  "mcpServers": {    "proofable": {      "type": "http",      "url": "https://mcp.proofable.me/mcp"    }  }}

{  "mcpServers": {    "proofable": {      "type": "http",      "url": "https://mcp.proofable.me/mcp"    }  }}

The installer writes the same connection for supported clients:

Claude Code installs the server and the workflow skills together:

Keep one Proofable connection per client. A marketplace plugin plus a manual entry creates a duplicate.

What agents can do

Outcome	Tools
Load the signed-in profile and current context	`proofable_context`
Find supported checks and their required inputs	`proofable_verifiers_catalog`
Check whether a qualifying proof already exists	`proofable_proofs_check`
Reuse a current proof or get the next verification step	`proofable_verify_or_guide`
Create or refresh a proof	`proofable_verify`
Prepare and submit a check needing another signer	`proofable_verify_prepare`, `proofable_verify_submit`
Find and read proofs	`proofable_proofs_get`
Update proof metadata or add feedback	`proofable_proofs_update`
Check, create, and load agent permissions	`proofable_agent_link`, `proofable_agent_create`, `proofable_agent_mount`

Call proofable_context once after connecting. Proofable reuses current proofs before starting another verification and returns Passed, Action needed, or Blocked.

The MCP tool reference lists every tool with its inputs and result shapes.

Servers and automation

Create an access key under Account → Access keys, store it as PROOFABLE_ACCESS_KEY, and send it as a Bearer token. Keep access keys out of source code, browser bundles, and chat.

json

{  "mcpServers": {    "proofable": {      "type": "http",      "url": "https://mcp.proofable.me/mcp",      "headers": {        "Authorization": "Bearer ${PROOFABLE_ACCESS_KEY}"      }    }  }}

{  "mcpServers": {    "proofable": {      "type": "http",      "url": "https://mcp.proofable.me/mcp",      "headers": {        "Authorization": "Bearer ${PROOFABLE_ACCESS_KEY}"      }    }  }}

Examples

Prompt injection test: hides AgentDojo attacks in a note your agent reads, runs the task under a scoped and a broad permission, and grades every run from its signed receipt.
Guarded agent action: makes one permission decision before host code runs a tool.

Build with Proofable

Use the Proofable SDK for application code, verification gates, and the CLI. This repository carries the MCP registry manifest, the host plugins, and the workflow skills; the server runs at https://mcp.proofable.me/mcp.

Support

Apache-2.0. Proofable is published by NEUS Network, Inc.

Source: README.md at commit 8460351

Tools

proofable_context

Session context

Return the signed-in Proofable profile and its current read-only context: proof index, agents, permissions, and verifier summary. Use once after sign-in.

Takes no parameters.

proofable_verifiers_catalog

Verifier catalog

Return supported check definitions with the inputs and networks each requires.

Takes no parameters.

proofable_proofs_check

Check proofs

Does this wallet already have the required proofs? Returns pass or fail, not records. Reading proof bodies needs a signed-in session, which is what unlocks proofable_proofs_get; signed-out callers get this check and can sign in to go further. Omit the wallet when signed in.

ParametersgateIdhandlewalletminCountnamespaceverifiersrequiredrequireAll

proofable_verify

Create proof

Create a proof directly for the signed-in account. Omit the wallet for your own account. If another signer is required, use proofable_verify_prepare and proofable_verify_submit.

ParametersdatachainoptionsverifierIdsrequiredwalletAddresssignedTimestamp

proofable_verify_prepare

Prepare signature request

Prepare a signature request for the selected Proofable checks. Returns the exact signing string, timestamp, chain, and hosted fallback. This call does not submit the check or create a proof.

ParametersdatachainoptionsverifierIdsrequiredwalletAddresssignedTimestamp

proofable_verify_submit

Submit signed verification

Submit a signed Proofable check using the same wallet, checks, data, and chain used to prepare it, plus the returned signing timestamp and signature. Creates a proof only when verification succeeds.

ParametersdatachainoptionssignaturerequiredverifierIdsrequiredwalletAddressrequiredsignedTimestamprequired

proofable_verify_or_guide

Verify or get next step

Resolve a verification request for the selected Proofable checks. Returns current qualifying proofs when they exist; otherwise returns the single next step. This tool does not create a proof.

ParametersdatachainoptionsrequireAllverifierIdsrequiredwalletAddress

proofable_proofs_get

Read proofs

Read a proof by qHash or search proofs by scope, tags, verifier, or text. With no filter, returns an index hint; scope=all pages metadata. Use include=content for proof bodies and includeComments with qHash for discussion. Omit identifier when signed in.

ParametersqtagsdepthlimitqHashscopeoffsetincludetraversetagPrefixidentifierverifierId+4 more

proofable_proofs_update

Update proof

Update a proof you own: title, tags, and visibility (public|unlisted|private). Setting visibility to private revokes public access, so confirm before making an already-shared proof private. Or leave feedback on an accessible proof. Send one kind of change per call: metadata, vote, or comment. Owners can vote on their own proofs. Delegated agents need manage_proofs.

ParametersvoteqHashrequiredtitleaddTagscommentparentIdremoveTagsvisibilitywalletAddressdisclosePortableProof

proofable_agent_link

Check agent permissions

Check whether an agent is set up to act for your profile, and what it may currently do. Given agentWallet (plus agentId when one account hosts several), it reports linked:true with the identity proof and active delegation, or link_required with the one next step. It does not create, change, or remove anything; to grant or change authority, use proofable_verify with agent-delegation.

ParametersagentIdprincipalagentWalletrequiredidentityQHash

proofable_agent_create

Create agent

Create or import an agent on your profile. Default: signed-in account. Optional separate account and controls. Generate and retain any dedicated key outside Proofable, then pass only its public address. Keep the same agentId on retries.

ParameterschainpresetskillsagentIdrequiredmaxSpendservicesagentTypeexpiresAtreturnUrlagentLabelagentWalletdescription+11 more

proofable_agent_mount

Load agent context

Load the agent identity, permissions, skills, and context into this project.

ParametersagentIdagentWalletidentityQHashcontrollerWalletrequiredResources

Version history

v0.1.10LatestNov 7, 2026
v0.1.8Nov 1, 2026
v0.1.7Oct 11, 2026
v0.1.6Oct 9, 2026
v0.1.5Oct 8, 2026
v0.1.4Oct 5, 2026
v0.1.3Sep 29, 2026
v0.1.2Sep 25, 2026
v0.1.1Sep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts