BanProof AI
REMOTE · BANPROOF.IO · SCANNED SEP 20
Audit creator scripts for TikTok Shop and Amazon policy violations. Returns flags and safe rewrites.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 349 tokens (~174/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the BanProof AI MCP server?
BanProof AI is a hosted endpoint at https://banproof.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · banproof.io
claude mcp add --transport http nimishrangani-banproof-mcp 'https://banproof.io/mcp'
{
"mcpServers": {
"nimishrangani-banproof-mcp": {
"url": "https://banproof.io/mcp"
}
}
} {
"servers": {
"nimishrangani-banproof-mcp": {
"type": "http",
"url": "https://banproof.io/mcp"
}
}
} [mcp_servers.nimishrangani-banproof-mcp] url = "https://banproof.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"nimishrangani-banproof-mcp": {
"type": "remote",
"url": "https://banproof.io/mcp",
"enabled": true
}
}
} openclaw mcp add nimishrangani-banproof-mcp --url 'https://banproof.io/mcp' --transport streamable-http
mcp_servers:
nimishrangani-banproof-mcp:
url: "https://banproof.io/mcp" {
"McpServers": {
"nimishrangani-banproof-mcp": {
"Transport": "http",
"Url": "https://banproof.io/mcp"
}
}
} assistant mcp add nimishrangani-banproof-mcp -t streamable-http -u 'https://banproof.io/mcp'
{
"mcpServers": {
"nimishrangani-banproof-mcp": {
"type": "http",
"url": "https://banproof.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +36
- Authorization: pass → unverified ▼ security
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Endpoint reachability: behind authorisation → reachable ▲ functional
- Stability: unverified → 0.47 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 12 Sept 26 −34
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.33 → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: unverified → pass ▲ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it. functional
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “audit_script” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Server version: 0.1.0 → 0.2.0 functional
- New tool “generate_appeal” functional
- “audit_script” added an optional parameter “product_url” cosmetic
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://banproof.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=banproof.io | CN=WE1,O=Google Trust Services,C=US | 19 Sept 2026 | 18 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | dc2a99443418f7de13c1af1a26de81f4 |
| SANs: banproof.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of banproof.io. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| banproof.io. | present | 15754 | 13 | Verified |
| banproof.io. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://banproof.io/mcp | Verified | 200 | |
| http (plaintext) | http://banproof.io/mcp | HTTPS enforced | 301 | https://banproof.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
audit_script Audit script for policy violations ~131
Audit a TikTok Shop or Amazon affiliate video script for policy violations. Detects: medical claims, guarantees, false certifications, unproven efficacy, urgency/scarcity language, fake social proof, income claims, and missing FTC disclosures (#ad/#sponsored). Returns flagged phrases, reasons, safe rewrites, and an overall risk level.
| Name | Type | Req | Description |
|---|---|---|---|
| product_url | string | – | Optional: URL of the product page being promoted. When provided, the script is cross-checked against the actual product claims — overclaims are flagged as additional violations. |
| script | string | yes | The full video script text to audit. |
No output schema declared.
No examples provided.
generate_appeal Generate platform violation appeal ~98
Generate a ready-to-submit appeal response for a TikTok, Amazon, or YouTube policy violation notice. Stays within TikTok's 800-character appeal limit. Paste the violation notice text you received and specify the platform.
| Name | Type | Req | Description |
|---|---|---|---|
| platform | string | yes | The platform that issued the violation: tiktok, amazon, or youtube. |
| violation_notice | string | yes | The full text of the violation notice or strike you received from the platform. |
No output schema declared.
No examples provided.
What is the BanProof AI MCP server?
BanProof AI is an MCP server listed in the public MCP registry as io.github.NimishRangani/banproof-mcp. Audit creator scripts for TikTok Shop and Amazon policy violations. Returns flags and safe rewrites. This page covers its hosted endpoint (https://banproof.io/mcp).
Is the BanProof AI MCP server safe to use?
BanProof AI scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the BanProof AI MCP server expose?
BanProof AI exposes 2 tools: audit_script, generate_appeal. Their descriptions and schemas cost roughly 229 tokens of context every time the server is loaded.
Does the BanProof AI MCP server require authentication?
No. We connected to BanProof AI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the BanProof AI MCP server still maintained?
BanProof AI is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.