purposebot-mcp
PurposeBot is an agent trust layer for the next web: agents and businesses can register identity, prove provenance, discover counterparties by earned trust, ask for API access decisions, transact through commerce workflows, and build reputation from verified interaction evidence.
This package connects Python-based MCP clients to PurposeBot with
purposebot-mcp. It exposes the hosted PurposeBot MCP tools for trust-ranked
discovery, API Trust provider registration, API access decisions, signed conduct
events, pending feedback, commerce recommendations, and
interaction/settlement-backed reputation.
The hosted endpoint is the source of truth for the tool catalogue, so new tools
(search_tools, submit_interaction_report, list_pending_feedback,
recommend_listings, create_api_trust_provider, request_api_trust_decision,
submit_api_trust_event, ...) appear automatically. This package is only the
stdio transport bridge; the trust, identity, payment, and provenance checks run
server-side in PurposeBot.
Usage
Requires Python 3.10+. Get an API key from your PurposeBot account.
PURPOSEBOT_API_KEY=pb_xxx python -m purposebot_mcp
or, after installing from PyPI:
PURPOSEBOT_API_KEY=pb_xxx purposebot-mcp
Claude Desktop / Cursor (mcpServers config)
{
"mcpServers": {
"purposebot": {
"command": "purposebot-mcp",
"env": {
"PURPOSEBOT_API_KEY": "pb_xxx"
}
}
}
}
Environment
| Variable | Required | Default | Notes |
|---|---|---|---|
PURPOSEBOT_API_KEY |
no | - | sent as X-API-Key; keyless mode supports first-key registration |
PURPOSEBOT_API_URL |
no | https://purposebot.ai |
origin only; use https://api.purposebot.ai or sandbox/self-host origin |
PURPOSEBOT_ALLOW_CUSTOM_HOST |
no | unset | set to 1 for non-PurposeBot self-hosts |
The wrapper validates the target URL before sending an API key. It only sends
keys to PurposeBot hosts by default, allows http://localhost for development,
rejects embedded credentials, and refuses HTTP redirects. Without
PURPOSEBOT_API_KEY, the wrapper can still call keyless MCP tools such as
begin_registration; protected tools return the hosted PurposeBot auth error.
Metadata
Release files for purposebot-mcp 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| purposebot_mcp-0.1.2.tar.gz | 7.9 kB | Without provenance | Details for purposebot_mcp-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| purposebot_mcp-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for purposebot_mcp-0.1.2-py3-none-any.whl |
Total release size: 14.0 kB
Release files / purposebot_mcp-0.1.2.tar.gz
| Download URL | purposebot_mcp-0.1.2.tar.gz |
|---|---|
| Size | 7.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ef40ce770d20181a6f7a14dc88a0c72032860a04c07f9e7d63f0a245a18c4d74
|
|
BLAKE2b-256 checksum How to use checksums |
61736afd3a272175ae9685437670813256c5e086af682e9eff6b5f6c87f12543
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Release files / purposebot_mcp-0.1.2-py3-none-any.whl
| Download URL | purposebot_mcp-0.1.2-py3-none-any.whl |
|---|---|
| Size | 6.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9ef77363db5cf1b59335c28635ce283a9e2f7c2283480cd84c587a4791c537c9
|
|
BLAKE2b-256 checksum How to use checksums |
cf8fbfd09c1a124d87b6e556c1066e809443672dc01e1aa9677587bd3ab873e1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for purposebot-mcp 0.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.