StrictScore

com.strictscorePublished by strictscore.comOfficial publisherv1.0.0Updated Oct 29, 2026

STRICT scores for crypto assets. Needs a Bearer API key from the Enterprise plan (US$99/mo).

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Remote MCP endpoint that gives an assistant access to StrictScore's STRICT scores for crypto assets, using an Enterprise API key.

What you can do
  • Retrieve STRICT scores for crypto assets through the hosted StrictScore endpoint.
  • No tool list is published, so the exact operations available are not documented in the supplied material.
When to use it
Consider it when you want an assistant to pull StrictScore's STRICT ratings on crypto assets while researching or comparing tokens, and you already have an Enterprise plan account.
Requirements
A remote streamable HTTP endpoint at strictscore.com; no local package or runtime is needed. A bearer API key from an Enterprise plan account (US$99/mo) must be sent in the Authorization header.
Before you install
The Authorization header carries a secret API key; keep it out of logs and shared configurations. Access requires a paid Enterprise subscription at US$99 per month. Requests and any asset queries go to the third-party StrictScore service.

Installation

In SourceWeft

  1. Open StrictScore in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.strictscore%2Fstrictscore/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "strictscore": {
      "type": "http",
      "url": "https://strictscore.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestOct 29, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.