Archived listing / no verified MCP endpoint/Other

ScamCheck listing

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

ScamCheck checks messages, links, and job offers for scams and returns a verdict, risk score, red flags, and next steps. The developer page documents per-account Bearer API keys and points MCP users to a third-party MCP host listing, while its own REST route is /api/v1/scan. It does not document https://scamcheck.tech/api/mcp, so this page is retained as an archived listing pending a verified endpoint.

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

Where it fits

People checking suspicious messages, links, or job offers who can use the provider's documented REST or third-party MCP host route.

  • Create a per-account API key on the developer page.
  • Use the third-party MCP host listing for MCP setup.
  • Check a suspicious message through the REST scan route.

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 returns 401 or 403. Check the key, its environment variable, and the permissions attached to it.
  • The key works in the provider dashboard but not in the client. Confirm the client sends it in the header the provider expects.
  • 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.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

ScamCheck documentationhttps://scamcheck.tech/dashboard/developerGitHub repositoryhttps://github.com/smijo-geek/scamcheck-mcp-server