Skip to content

MCP servers › io.alphagrowth › data

MCP server · registry snapshot 2026-10-27 · last tested 2026-10-27

io.alphagrowth/data

AlphaGrowth — the publisher's title

by alphagrowth.io · domain (the registry's namespace rule)Website ↗

AlphaGrowth is a crypto growth firm that grows protocols' TVL and liquidity and publishes free data. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-10-27version 1.0.1streamable HTTP22 tools

Summary

io.alphagrowth/data is a remote MCP server listed in the official MCP registry at version 1.0.1, under the namespace of the domain alphagrowth.io. On 2026-10-27 ProtocolProbe connected to it in read-only mode and read its inventory: 22 tools, 0 resources and 0 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

  • met: Registry entry is active and says how to run it
  • not met: Source repository link opens
  • not applicable: Repository is not archived
  • not applicable: Code pushed to the repository in the 90 days before our check
  • not applicable: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason

Operate this server? Correct a fact · README badge · Run the checks yourself

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Tools
22
Last tested
2026-10-27

Tool list size

6,179 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (22 tools). Counted with Anthropic's token counter on 2026-10-27, from the tool list we read on 2026-10-27. Median across 23,424 counted servers: 2,725 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-10-27 (alphagrowth.io), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.0.1).

Add to your client

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-10-27
Mode
read-only (no tool calls)
Latest version
1.0.1, published 2026-10-27 (registry, as of the 2026-10-27 snapshot)
First listed version
2026-10-26 (earliest version still in the registry; older removed versions would be earlier)
Version history
2 versions listed, 2026-10-26 to 2026-10-27; 2 in the 90 days before the 2026-10-27 snapshot.
Most recent 2 versions
  • 1.0.1 · 2026-10-27
  • 1.0.0 · 2026-10-26
(versions still listed in the registry only)
Registry data
snapshot 2026-10-27
Package and repository
checked 2026-10-27
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-10-26, listed on 2026-10-27 with version 1.0.1 (published 2026-10-27).

Source: the official MCP Registry list on 2026-10-26 and on 2026-10-27.

What it is

What does this server offer?

Observed inventory
22tools
0resources
0prompts

None of its 22 tools are described as changing anything. For 22 the reading was uncertain, so no mark is shown.

  • list_keywordson 8 other servers

    “The keywords whose results are tracked.”

    Publisher declares: read-only yes · open-world no

    Takes no inputs.

  • “The sources that have produced results, for example twitter_spaces, tweets_en or tweets_ja.”

    Publisher declares: read-only yes · open-world no

    Takes no inputs.

  • search_resultson 2 other servers

    “Recorded search results, newest first.”

    Publisher declares: read-only yes · open-world no

    6 inputs
    • offsetinteger“Rows to skip, for paging through `total`.”
    • querystring“Free text to match.”
    • sourcestring“Restrict to one source, from list_sources.”
    • limitinteger“Rows to return, at most 100.”
    • keyword_idinteger“Restrict to one keyword, by id from list_keywords.”
    • search_instring“Where to match `query`: result titles, Twitter Space transcripts, or both.”
  • get_transcripton 36 other servers

    “The full transcript of an imported Twitter Space, by the broadcast_id that search_results reports.”

    Publisher declares: read-only yes · open-world no

    1 input, 1 required
    • broadcast_idintegerrequired“From the broadcast_id field of a search_results entry.”
  • list_transcribed_spaces

    “Twitter Spaces among the matching results whose import produced a transcript, one entry per broadcast with the keywords that found it.”

    Publisher declares: read-only yes · open-world no

    4 inputs
    • querystring“Free text to match.”
    • limitinteger“Entries to return, at most 100.”
    • keyword_idinteger“Restrict to one keyword, by id.”
    • search_instring“Where to match `query`.”
  • find_projectson 2 other servers

    “Finds crypto projects whose name or symbol contains the query, largest TVL first, with slug, category, TVL and market cap.”

    Publisher declares: read-only yes · open-world no

    2 inputs, 1 required
    • limitinteger“Number of projects, 1 to 20.”
    • querystringrequired“Part of a project's name or symbol.”
  • project_metrics

    “A crypto project's current metrics from AlphaGrowth: TVL, price, market cap, volume, revenue, users and social followers with 1d/7d/30d changes, plus its description, categories, chains and links.”

    Publisher declares: read-only yes · open-world no

    1 input, 1 required
    • slugstringrequired“The project's slug; find it with find_projects.”
  • project_community

    “How fast a crypto project's community is growing: followers or members per network (X/Twitter, Telegram, Discord, Reddit) with 1d/7d/30d percent changes and one point per day for up to 90 days.”

    Publisher declares: read-only yes · open-world no

    3 inputs, 1 required
    • daysinteger“Days of daily history, counting today.”
    • networkstring“Only this network; all four when omitted.”
    • slugstringrequired“The project's slug; find it with find_projects.”
  • rank_projects

    “Ranks crypto projects by a metric such as TVL, market cap, price, revenue or followers (or its 1d/7d/30d change), optionally within a category or chain, 50 per page.”

    Publisher declares: read-only yes · open-world no

    5 inputs
    • categorystring“Only projects in the category with this slug.”
    • chainstring“Only projects on this chain: the `chain_slug` of a row from the chains tool.”
    • pageinteger“Page number, 50 projects per page.”
    • sort_bystring“The metric to rank by.”
    • sort_orderstring“desc for the highest first, asc for the lowest.”
  • project_fundingon 1 other server

    “A crypto project's funding rounds (oldest first, with date, amount, type and valuation where known), the investors behind them and the total raised.”

    Publisher declares: read-only yes · open-world no

    1 input, 1 required
    • slugstringrequired“The project's slug; find it with find_projects.”
  • recent_funding_roundson 1 other server

    “The most recent crypto funding rounds, newest first, with project, category, amount, type and investors, optionally within a category, 50 per page.”

    Publisher declares: read-only yes · open-world no

    2 inputs
    • categorystring“Only rounds of projects in the category with this slug.”
    • pageinteger“Page number, 50 rounds per page.”
  • top_investors

    “The top 100 crypto investors ranked by number of projects funded or by total amount invested, with their first 20 funded projects (projects_more counts the rest), 50 per page.”

    Publisher declares: read-only yes · open-world no

    2 inputs
    • pageinteger“Page number, 50 investors per page.”
    • sort_bystring“projects ranks by projects funded, amount by USD invested.”
Show 10 more tools
  • investor_profile

    “A crypto investor's public profile (type, location, website, industries, investment criteria) and its investments, newest first, 50 per page.”

    Publisher declares: read-only yes · open-world no

    2 inputs, 1 required
    • pageinteger“Page number of the investments, 50 per page.”
    • slugstringrequired“The investor's slug; find it with top_investors or recent_funding_rounds.”
  • chains

    “Blockchains ranked by TVL with price, market cap, 1d/7d TVL change and how many projects run on each, 50 per page.”

    Publisher declares: read-only yes · open-world no

    2 inputs
    • pageinteger“Page number, 50 chains per page.”
    • querystring“Only chains whose name contains this text.”
  • chain_metrics

    “A blockchain's metrics as on AlphaGrowth's chain compare page.”

    Publisher declares: read-only yes · open-world no

    1 input, 1 required
    • slugstringrequired“The chain's slug as listed by chains.”
  • “Protocols ranked by fees or revenue for the latest completed day, with the 24h change, the chains they earn on and their version splits, 50 per page.”

    Publisher declares: read-only yes · open-world no

    3 inputs
    • pageinteger“Page number, 50 protocols per page.”
    • sort_bystring“The column to sort by.”
    • sort_orderstring“desc for the highest first, asc for the lowest.”
  • treasury_companies

    “Public companies holding crypto (BTC, ETH, SOL and others) on their balance sheet: market cap, NAV, mNAV and holdings per token, 50 per page.”

    Publisher declares: read-only yes · open-world no

    1 input
    • pageinteger“Page number, 50 companies per page.”
  • dao_treasuries

    “Lists DAO treasuries worth more than $500, largest first: total USD value, 24h change, category, top tokens and main chain.”

    Publisher declares: read-only yes · open-world no

    3 inputs
    • limitinteger“Page size, 1 to 100.”
    • offsetinteger“Number of DAOs to skip.”
    • projectstring“Only the DAO of the project with this slug.”
  • dao_treasury_snapshot

    “Every listed DAO's treasury value in USD as of one UTC day (the last sample up to 6 days before it), largest first, for any day since 2024-07-24 up to yesterday (default: yesterday).”

    Publisher declares: read-only yes · open-world no

    1 input
    • datestring“The day, YYYY-MM-DD, from 2024-07-24 to yesterday (default: yesterday, UTC).”
  • dao_treasury_history

    “Daily total treasury value in USD of one DAO, one point per UTC day (the day's last sample), daily since 2024-07-24; defaults to the whole history.”

    Publisher declares: read-only yes · open-world no

    3 inputs, 1 required
    • daointegerrequired“The DAO id, as listed by dao_treasuries.”
    • fromstring“First day, YYYY-MM-DD (default: first day with data).”
    • tostring“Last day, YYYY-MM-DD, not after today (default: latest).”
  • dao_holdings_history

    “Daily token holdings of one DAO treasury (amount, USD value and price per token, one point per token per UTC day), daily since 2024-07-24.”

    Publisher declares: read-only yes · open-world no

    3 inputs, 1 required
    • daointegerrequired“The DAO id, as listed by dao_treasuries.”
    • fromstring“First day, YYYY-MM-DD (default: 29 days before `to`).”
    • tostring“Last day, YYYY-MM-DD, not after today (default: today, UTC).”
  • dao_treasury

    “One DAO treasury by id: total USD value, 24h change, category, top tokens and main chain.”

    Publisher declares: read-only yes · open-world no

    1 input, 1 required
    • idintegerrequired“The DAO id, as listed by dao_treasuries.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-27.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
100% of 47
Tools with a description
100% of 22
Typical description length
236 characters

The tool set

Counted from the listing

Tools
22
Size of the list
about 4,107 tokens for an agent to load (characters ÷ 4)
Naming
20 of 22 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 22 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-27 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://alphagrowth.io/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "data": {
      "url": "https://alphagrowth.io/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "data": {
      "type": "http",
      "url": "https://alphagrowth.io/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"data","type":"http","url":"https://alphagrowth.io/mcp"}'
Claude Code
claude mcp add --transport http data https://alphagrowth.io/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "data": {
      "type": "streamableHttp",
      "url": "https://alphagrowth.io/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "data": {
      "httpUrl": "https://alphagrowth.io/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.data]
url = "https://alphagrowth.io/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "data": {
      "url": "https://alphagrowth.io/mcp"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://alphagrowth.io/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint alphagrowth.io/mcpSession openedmatchesour test · 2026-10-27
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-10-27

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
  • Does not applyRepository is not archivedNo public GitHub repository to read.
  • Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
  • Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-27. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.alphagrowth/data

Answered from the data above

Who publishes io.alphagrowth/data?

The registry ties the namespace io.alphagrowth to the domain alphagrowth.io; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.

Does io.alphagrowth/data need an API key or sign-in?

It opened a session without any credential on 2026-10-27. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.alphagrowth/data been security tested?

Partly. 2 of the 14 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security verdict is published before verification.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (we call no server's tools)

We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-27
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: not applicable

2 exercised12 not run (reason given)4 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 2
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
Not run, with the reason · 12
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 4
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-10-27, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 781 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 22 tools, 0 resources, 0 prompts.
  4. 4,513 msFinished: 2 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added in the weekly update
listed 2026-10-27; not classified yet
Pricing modelAI-classified
pending: added in the weekly update
the website is not read yet
Programming language
does not apply
no existing GitHub repository (server declares no repository link, so there is nothing to fetch)
Hosting type
registry · 2026-10-27
MCP capability
tools
our test · 2026-10-27
Transport
streamable HTTP
registry · 2026-10-27
Required credentials
none declared
registry · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-10-27
Lifecycle status
registry · 2026-10-27
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
not stated
no readable GitHub owner to describe
Maintenance
does not apply
server declares no repository link, so there is nothing to fetch
Environment
the publisher's infrastructure
where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.alphagrowth/data: MCP server record.” Data checked 2026-10-27. https://protocolprobe.com/mcp/servers/io.alphagrowth/data

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 1 of 2 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.alphagrowth/data)](https://protocolprobe.com/mcp/servers/io.alphagrowth/data)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology