MCP servers › com.agenticfinancegraph › agentic-finance-graph

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

com.agenticfinancegraph/agentic-finance-graph

Ledger of AI-agent money on Base: ranked agents, payments, detections, free checks before you pay — the publisher's description

5 of 5 record checks metRead-only · tools listed 2026-10-24Topic: finance-and-payments · AI-classifiedversion 1.7.0JavaScriptstreamable HTTP25 tools

Summary

com.agenticfinancegraph/agentic-finance-graph is a remote MCP server listed in the official MCP registry at version 1.7.0. On 2026-10-24 ProtocolProbe connected to it in read-only mode and read its inventory: 25 tools, 3 resources and 5 prompts.

Record checks

5 of 5 record checks met · 4 do not apply

met: Registry entry is active and says how to run it
met: Source repository link opens
met: Repository is not archived
met: Code pushed to the repository in the 90 days before our check
met: 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: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Sign-in: none needed to open a session
Repository: public
Tools: 25
Topic: finance-and-paymentsAI-classified
Last tested: 2026-10-24

Add to your client

How fresh this is

Live-tested

yes, a real session (not a text-only review)

Last tested

2026-10-24

Mode

read-only (no tool calls)

Latest version

1.7.0, published 2026-10-23 (registry, as of the 2026-10-24 snapshot)

First listed version

2026-10-06 (earliest version still in the registry; older removed versions would be earlier)

Version history

5 versions listed, 2026-10-06 to 2026-10-23; 5 in the 90 days before the 2026-10-24 snapshot.

Most recent 5 versions

1.7.0 · 2026-10-23
1.5.0 · 2026-10-12
1.4.0 · 2026-10-12
1.2.0 · 2026-10-12
1.1.0 · 2026-10-06

(versions still listed in the registry only)

Registry data

snapshot 2026-10-24

Package and repository

checked 2026-10-24

Engine

mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

Version 1.5.0 (published 2026-10-12) → 1.7.0 (published 2026-10-23), between the registry lists of 2026-10-23 and 2026-10-24.

The publisher published no GitHub release note for version 1.7.0: the repository has no release tagged for it.

Source: the official MCP Registry list on 2026-10-23 and on 2026-10-24; release notes from the GitHub Releases API, checked 2026-10-24.

What it is

What does this server offer?

Observed inventory

25tools

3resources

5prompts

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

market_stateon 3 other servers
“The ledger's headline figures for AI-agent money, each with its value, unit, measurement time and definition id.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
- compactboolean“Leave out the reading notes and the previous-sample block (figures, data quality and licence stay)”
find_agenton 4 other servers
“Look up an ERC-8004 agent by token id on Base, slug, wallet address (0x...) or the name it declares.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- querystringrequired“Token id (57657), slug (8004-base-57657), wallet (0x...), a declared name, or up to 25 ids separated by commas”
agent_recordon 2 other servers
“The free record of one ranked agent: rank with evidence, bindings, and its 25 newest payments with counterparties.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- idstringrequired“Token id, slug or wallet address”
ranked_agents
“The top ranked agents (L7 and above: a bound wallet was seen paying money out of the agent's control after registration).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs
- limitinteger
- min_levelinteger“Only agents at or above this liveness level”
- sort_bystring“Order within each level: lifetime counted USD (default), distinct counterparties, or number of counted payments”
detections
“Anomalies our detectors logged, newest first: drain-shaped payments (each with the share of the wallet's balance it took), retry storms, mint bursts, fleet-funding fan-outs (layering_fan), owner chan…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
7 inputs
- agentstring“Optional agent id (act_8453_N or token id)”
- limitinteger
- kindstring
- severitystring
- sincestring“ISO time; only detections at or after it”
- live_onlyboolean“Only detections that are live incidents”
- compactboolean“Leave out the glossaries and tier notes”
definitionon 2 other servers
“The frozen definition of a metric: what it counts, the method, what it excludes and what it does not claim.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- idstringrequired“Definition id, e.g.”
metric_historyon 1 other server
“The history of one measured metric from the ledger's archive (daily points, plus 5-minute points for the last 48 hours).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
- keystringrequired“Metric key, e.g.”
- rangestring
since_last
“One measured figure with the stored sample it moved from: current, prior, delta, delta_ratio, both timestamps, definition id, unit, and whether the move is material under the published thresholds.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
- metric_idstringrequired“Metric key (actors_l7_plus) or definition id (rank.l7plus.v1)”
- windowstring
counterparty_preview
“For one receiving address on Base (or an x402 resource URL listed in the Bazaar): how many counted payments registered agents made into it, how many distinct agents and how many at L7 or above, first…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
- addressstring“0x address on Base, or an x402 resource URL; omit for the top endpoints”
agent_statement
“The latest 3-hour statement for one ranked agent: payments out split into spend, routing hops and payments whose receipt is not read yet; what left its control; income; open flags; the hash of the pr…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- idstringrequired“Agent token id, slug or bound wallet”
evidence_pack_quote
“Price and how to buy a dated evidence pack over x402 (USDC on Base, 1 to 30 cents).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 2 required
- kindstringrequired
- idstringrequired“Agent token id, slug or wallet; for counterparty and venue, the 0x address”
- paytostring“precheck only, optional: the 0x address you are about to pay”
pay_check
“One free call before your agent pays or hires another: its latest statement (stale, age, chain_ok, flags), live incidents, its detections in the last 72 hours, the token approvals its wallet has give…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- agentstringrequired“Agent token id, slug or bound wallet”

Show 13 more tools

payer_set
“The wallets observed paying one agent (income into its bound wallets, plus counted payments from other registered agents), up to 250, with payments, USD and first and last paid; and how much of its E…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs, 1 required
- agentstringrequired“Base ERC-8004 token id, act_8453_N, or a ranked agent's slug or bound wallet”
- limitinteger“How many payers to list (largest by USD first)”
agent_stability
“The behaviour clock for one ranked agent: run_days (complete UTC days since the last break in its own payment behaviour, by a CUSUM on payments, USD, payees and new-payee share against its own histor…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- agentstringrequired“Agent token id, slug or bound wallet”
agent_independence
“For one ranked agent: its independence score (1 if it paid, in 30 days, an address with demand from three or more operator sets; else half the best score of an agent outside its set that paid one of …”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- agentstringrequired“Agent token id, slug or bound wallet”
ladder_dynamics
“The whole-cohort document: cumulative incidence of the four competing exits (drained, abandoned, dormant, none) at 30, 60, 90 and 180 days with the numbers at risk and the restricted mean time withou…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
verify_sum_log
“Trust nothing you did not recompute.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs
- agentstring“Optional: an agent token id whose proof to climb”
- previous_headobject“Optional: the sum-log head you kept: { leaves, root }”
- previous_statement_headobject“Optional: the statement-log head you kept: { tree_size, root_hash }”
agent_pattern
“The out-of-character score of an agent's newest counted payment against its own earlier payments (behaviour.out_of_character.v2: amount out of its distribution, a new payee at a new size, a never-pai…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- agentstringrequired“Agent token id, act_8453_N, slug or bound wallet”
payee_facts
“What the chain and our ledger say about an address an agent is about to pay (payee.facts.v2): its code kind (plain key, contract, EIP-7702 delegated) and whether the delegate matches a known sweeper …”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 1 required
- payeestringrequired“The 0x address to be paid”
- agentstring“Optional: the paying agent (token id, slug or bound wallet), for the two per-agent facts”
- amount_usdnumber“Optional: the amount about to be paid, in USD”
gate_checkon 4 other servers
“One call before an agent pays: the payee facts, the agent's own context from our ledger (what it paid in the period, how often, whether and when it first paid this payee, how many new payees today), …”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
5 inputs, 3 required
- agentstringrequired“The paying agent: token id, act_8453_N, slug or bound wallet”
- payeestringrequired“The 0x address to be paid”
- amount_usdnumberrequired“The amount in USD”
- policy_namestring“A named policy (default log-only)”
- policyobject“Or your own policy object in the AP2 vocabulary; unknown keys fail closed”
agent_pass
“What the ledger measured about one registration at its last evaluation under agent.pass.v2, valid three hours: published level L7+, no open harm-kind incident, a counted payment in the last 30 days, …”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input, 1 required
- agentstringrequired“Agent token id, act_8453_N, slug or bound wallet”
blast_radiuson 6 other servers
“For an agent (L8 or above) or one of its bound wallets: priced stablecoin and token balances and ETH in USD at one block, the EIP-7702 delegate if any with its code hash and known sweeper family, and…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
- agentstring“Agent token id, act_8453_N or slug”
- walletstring“Or one 0x wallet address”
canary_register
“Register the public part of a decoy you planted: kind address|key|url|apikey|tool|x402 with exactly one target (address, url_sha256, key_sha256, tool_name or resource_path), a label, the triggers to …”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
1 input, 1 required
- registrationobjectrequired“{canary_id (32-64 hex), kind, label, watch[], planted_at, and one of address | url_sha256 (+url_host) | key_sha256 | tool_name (+description_sha256) | resource…”
canary_status
“Every canary you registered, with the watcher's last reading (nonce, code, balance, checks) and the newest 20 events per canary (trigger, severity, evidence, whether you declared it a test, the readi…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
Takes no inputs.
list_metricson 19 other servers
“Every metric the ledger measures or archives: key, unit, definition id, whether it is a headline figure, its first stored sample, and the date from which its history compares across our own changes (…”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
- filterstring“Optional: part of a key, a definition id or a word, e.g.”

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-24.

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: 84% of 45
Tools with a description: 100% of 25
Typical description length: 567 characters

The tool set

Counted from the listing

Tools: 25
Size of the list: about 6,987 tokens for an agent to load (characters ÷ 4)
Naming: 23 of 25 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 25 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-24 (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://agenticfinancegraph.com/mcp

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "agentic-finance-graph": {
      "url": "https://agenticfinancegraph.com/mcp"
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "agentic-finance-graph": {
      "type": "http",
      "url": "https://agenticfinancegraph.com/mcp"
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"agentic-finance-graph","type":"http","url":"https://agenticfinancegraph.com/mcp"}'

Claude Code

claude mcp add --transport http agentic-finance-graph https://agenticfinancegraph.com/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://agenticfinancegraph.com/mcp --transport http

The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
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). 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 verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Remote endpoint agenticfinancegraph.com/mcp	Session opened	matches	our test · 2026-10-24
No credential declared as required	Opened a session without any credential	matches	our test · 2026-10-24
Repository github.com/AgenticFinanceGraph/agentic-finance-graph-mcp	Opens publicly	matches	api.github.com · 2026-10-24

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: com.agenticfinancegraph
GitHub owner: a personal account (AgenticFinanceGraph)

Repository: github.com/AgenticFinanceGraph/agentic-finance-graph-mcp
Stars: 0
Repository age: 0–30 days
Last push: 0–30 days ago
Archived: no
Security policy: SECURITY.md

Source: the registry entry and api.github.com · 2026-10-24; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

5 of 5 record checks met · 4 do not apply

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: 0 stars (ranked from 10)

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
MetSource repository link opensThe linked GitHub repository is public.
MetRepository is not archivedNot archived.
MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
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-24. 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 com.agenticfinancegraph/agentic-finance-graph

Answered from the data above

Is com.agenticfinancegraph/agentic-finance-graph safe to install?

We do not rate servers as safe or unsafe. 5 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does com.agenticfinancegraph/agentic-finance-graph need an API key or sign-in?

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

Has com.agenticfinancegraph/agentic-finance-graph been security tested?

Partly. 4 of the 15 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.

Does com.agenticfinancegraph/agentic-finance-graph publish a security policy?

Yes: its repository has a public security policy (github.com/agenticfinancegraph/agentic-finance-graph-mcp/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.

Where is the source code of com.agenticfinancegraph/agentic-finance-graph?

In github.com/AgenticFinanceGraph/agentic-finance-graph-mcp, which opens publicly.

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.

Similar servers

Same topic · AI-read

io.github.ccxt/ccxt-mcpCCXTcompare with this one
cloud.basebalance/basebalancebasebalance.cloud — x402 RPC & MCP gatewaycompare with this one
io.github.JerBouma/financetoolkitFinance Toolkitcompare with this one
io.github.atilaahmettaner/tradingview-mcpTradingMCPcompare with this one
io.github.dgunning/edgartoolsEdgarToolscompare with this one
io.github.vybenetwork/solana-mcp-vybeSolana MCP by Vybecompare with this one

Active servers whose topic is also “finance-and-payments”, most GitHub stars first. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

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-24

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: exercised
Fake assistant turns: exercised
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: not applicable

4 exercised11 not run (reason given)3 not applicable

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

Exercised · 4

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
12Hidden content
audience-hidingChecks resources that hide content from the user.exercised
13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.exercised

Not run, with the reason · 11

3Real execution
real-executionCalls 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-leakPlants 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
ssrfChecks 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-confirmationChecks 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-handlingSends 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
samplingChecks 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-dataChecks 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-boundaryChecks 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-channelChecks 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
16Sign-in redirect
open-redirectChecks 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-deputyChecks 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 · 3

14Token passthrough
token-passthroughChecks 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-validationChecks 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-schemeChecks 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-24, 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.

0 msStarted a read-only session with the server's remote endpoint
1,256 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 25 tools, 3 resources, 5 prompts.
8,155 msFinished: 4 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

finance-and-payments

AI-classified · 2026-10-23 · from version 1.5.0 (same title and description)

Pricing modelAI-classified

no value

No value: the AI answer was held back because the quoted text did not clearly support it. · from version 1.5.0 (same website)

Programming language

JavaScript

api.github.com · 2026-10-24

Hosting type

remote (hosted by the publisher)

registry · 2026-10-24

MCP capability

prompts, resources, tools

our test · 2026-10-24

Transport

streamable HTTP

registry · 2026-10-24

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-24

Lifecycle status

active

registry · 2026-10-24

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

owner: a personal account · repository age: 0–30 days · stars: 0–9

api.github.com · 2026-10-24

Maintenance

active

api.github.com · 2026-10-24

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. “com.agenticfinancegraph/agentic-finance-graph: MCP server record.” Data checked 2026-10-24. https://protocolprobe.com/mcp/servers/com.agenticfinancegraph/agentic-finance-graph

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](https://protocolprobe.com/api/v1/badge/com.agenticfinancegraph/agentic-finance-graph)](https://protocolprobe.com/mcp/servers/com.agenticfinancegraph/agentic-finance-graph)

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