Archived listing / no verified MCP endpoint/Other

prompt-injection-check listing

No MCP endpoint is published. This listing is retained for reference.

prompt-injection-check was listed as a pay-per-call prompt injection check for untrusted text, with per-span evidence and offsets and a published 24-case known-answer set at $0.01 per text through x402 on Base. The cited Bitbucket repository returned 404, and the published endpoint https://prompt-injection-check.onrender.com/mcp also returned 404 on 2026-11-16. The pricing and evidence claims are unverified, and this page is retained as a reference only.

Archived listingNo verified MCP endpoint is published. This page is retained for reference only.
No MCP endpoint Reviewed 2026-11-16
About

Where it fits

Teams evaluating prompt injection filters, pending a reachable provider source.

  • Check an email body for prompt injection, if the service returns.
  • Scan tool output for injected instructions.
  • Review per-span evidence with offsets.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • Authentication fails or no tools appear. The listing does not verify the provider's credential flow; check its documentation before retrying.
  • The endpoint responds but rejects tool calls. Confirm the current address and any account, key, or payment requirement with the provider.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.