One MCP server · software-only · USD 500
Know what it can do
before an agent does it.
We inspect one MCP server at one revision, map what each tool and resource can read or change, run ten agreed protocol checks in a disposable environment, and return an evidence-backed go/no-go report.
Start with metadata or a public repository. No credentials, production data, payment, or server access until the scope and handling rules are accepted in writing.
One revision · up to eight tools/resources · ten checks · one correction pass.
A small, inspectable review
Map. Exercise.
Decide.
01Freeze the repository revision, runtime, transport, advertised surface, and data boundary.
02Map each tool and resource to reads, writes, external calls, credentials, and failure impact.
03Run ten agreed checks for protocol behavior, invalid input, authority boundaries, and safe failure.
04Return the evidence packet, failure ledger, and a narrow go/no-go decision.
What comes back
A decision tied to evidence.
The result keeps the advertised protocol surface, actual authority, executed cases, and unresolved risks together.
Authority map
For each reviewed tool and resource: inputs, outputs, reads, writes, external calls, credential use, human approval points, and worst credible failure.
Protocol packet
Frozen revision and environment, tool/resource inventory, ten agreed calls or rejection cases, sanitized logs, observed outputs, and reproducible commands.
Go/no-go report
A failure ledger ranked by impact, the safe operating boundary for this revision, and the smallest next fix or separate implementation scope.
Code and protocol, not theatre
Read-only labels are checked against behavior.
Tool annotations are useful signals, but they are not enforcement. The review looks for the controls underneath them: storage modes, allowlists, input bounds, external calls, authentication assumptions, and failure behavior.
You provide
A public or rights-cleared repository revision, setup instructions, the intended client and transport, and a description of sensitive data or actions without sharing the data itself.
We agree first
The exact surface, ten checks, disposable test environment, permitted network calls, secrets handling, success signals, retention, and delivery format.
You keep control
No production write, destructive operation, credential, or private dataset is used unless separately authorized and scoped. Public proof never includes customer material.
Executed public sample
A multilingual knowledge server, checked end to end.
The sample reviews the public Local Knowledge Terminal MCP bridge using the official Python MCP SDK and a project-owned PocketPolyglot fixture.
Frozen at LKT e750e5a
Two tools. One resource. Fourteen passing tests.
The SDK listed and called both tools, read the status resource, and traced a Japanese query to Chinese evidence and its source hash. The report records a narrow GO for local read-only use and a NO-GO for direct remote exposure without authentication.
This is project-owned evidence, not a customer result, penetration test, or production certification.
Sample decision
GO locally.
NO-GO remotely.
2Read-only tools advertised and exercised through MCP.
1Bounded status resource returned no database path.
0Prompts, write tools, model calls, or production data.
Working terms
The server and checks are fixed before payment.
Timing
Delivery is within seven business days after secured payment, repository access, working setup instructions, and every agreed test dependency are available. Only one MCP review is active at a time.
Correction pass
One consolidated list of factual corrections is included within seven calendar days after delivery. A new revision, server, transport, tool, resource, or test case is a new scope.
Cancellation and refund
Cancel before private access or execution begins for a full refund. Once work starts, USD 100 covers environment setup, USD 150 the authority map, USD 150 the protocol packet, and USD 100 the final report; only undelivered items are refunded.
Exclusions
No fix implementation, penetration test, security certification, OAuth build, production deployment, destructive live testing, SLA, performance guarantee, or ongoing monitoring is included.
MCP Boundary Review · USD 500
Start with the smallest server boundary that matters.
Describe the repository, protocol surface, and intended client first. If it fits, both sides accept the exact checks, handling rules, and delivery terms before payment. Direct-site clients receive a Stripe request; marketplace clients keep the contract and payment on that marketplace.