Archived listing / no verified MCP endpoint/Development

Stack Facts: paid EOL, CVE and LLM price checks listing

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

Stack Facts checks a package for malware, known vulnerabilities, exploited CVEs, and end-of-life dates, and reports LLM prices. Answers are signed, and paid calls use USDC via x402 with no account or API key. The provider tunnel returned HTTP 503 when checked, so the endpoint is not currently usable; the page is retained as an archived listing with the capability summary intact.

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

Where it fits

Developers and security reviewers who need signed package and model-pricing checks once the service returns.

  • Check a package for known vulnerabilities and exploited CVEs.
  • Look up end-of-life dates for a dependency.
  • Compare LLM prices with a signed answer.

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.

  • The provider's page did not load when we checked. Confirm the current setup steps before troubleshooting the client.
  • 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.

Stack Facts: paid EOL, CVE and LLM price checks documentationhttps://g5joilnmeep4ntz3nwezxt5dmu.srv.us/llms.txt