MCP servers › io.github.pouriaetab › llmledger
MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23
io.github.pouriaetab/llmledger
Which AI model, and what it costs: LiteLLM prices, Arena ratings and price history. — the publisher's description
Summary
io.github.pouriaetab/llmledger is a local MCP server listed in the official MCP registry at version 0.2.0. On 2026-10-23 ProtocolProbe started its published package in an isolated sandbox in read-only mode and read its inventory: 11 tools, 1 resource and 1 prompt.
Record checks
7 of 8 record checks met · 1 does 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
- not met: Repository publishes a security policy (SECURITY.md)
- met: Package names its licence with a standard (SPDX) identifier
- met: The version the registry lists can be installed and is not withdrawn
- not applicable: npm package carries build provenance (attestation)
- met: No known critical or high advisory in the package or its dependencies
- #14,745 of 15,112 packages by monthly downloads, tied with 367 others
- 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
- local package
- Transport
- standard input/output
- Package
- PyPI · listed version current
- License
- MIT
- Dependencies
- no known high or critical advisories
- Repository
- public
- Tools
- 11
- Described as changing data
- 1 of 11 toolsAI-classified
- Topic
- finance-and-paymentsAI-classified
- Last tested
- 2026-10-23
Worth knowing before you connect it
- 1 tool is described as changing something (log_run): our AI model's reading of the descriptions, not something we tested. We did not call it.
Each line comes from a section below, with its source and date.
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-10-23
- Mode
- read-only (no tool calls)
- Latest version
- 0.2.0, published 2026-10-21 (registry, as of the 2026-10-23 snapshot)
- First listed version
- 2026-10-17 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 10 versions listed, 2026-10-17 to 2026-10-21; 10 in the 90 days before the 2026-10-23 snapshot.(versions still listed in the registry only)
Most recent 10 versions
0.2.0· 2026-10-210.1.9· 2026-10-210.1.8· 2026-10-200.1.7· 2026-10-190.1.6· 2026-10-190.1.4· 2026-10-190.1.3· 2026-10-190.1.2· 2026-10-180.1.1· 2026-10-170.1.0· 2026-10-17
- Registry data
- snapshot 2026-10-23
- Package and repository
- checked 2026-10-23
- Engine
- mcp-runtime-engine@0.1.0 · sdk@1.32.0
Changes since the last refresh
New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 0.2.0 (published 2026-10-21).
Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.
What it is
What does this server offer?
Observed inventory1 of 11 tools are described as changing something (creating, editing, deleting, sending or running).
“List the highest rated models for a kind of work within price, prompt size, ability and maker limits, each at its cheapest listing with its rating; or, with `name`, look one model up and list every h…”
Publisher declares: read-only yes · idempotent yes · open-world no
7 inputs
taskstring“The kind of work, as Arena rates it”max_output_pricenumber or null“Highest answer price, dollars per 1M tokens”min_contextinteger or null“Smallest prompt size the model must take, in tokens”needsarray“What the model must be able to do”makerstring or null“Only this maker, for example anthropic or openai”limitinteger“How many models to list (up to 200 for the whole catalogue)”namestring or null“Look up one model by name instead of browsing: all its listings”
“Compare 2 to 6 named models for a kind of work: rating, prices, cost per task (or how fast each uses a Claude or ChatGPT plan), the pick, and for each model the share of answer tokens at which it wou…”
Publisher declares: read-only yes · idempotent yes · open-world no
6 inputs, 1 required
modelsarrayrequired“2 to 6 model names, for example claude-opus-5.5, gpt-6.1-sol”taskstring“The kind of work, as Arena rates it”input_tokensinteger“Prompt tokens per task”output_tokensinteger“Answer tokens per task, including hidden thinking”answer_tokensobject or null“Answer tokens per model when they differ, by the names given”paystring“api: dollars; claude or chatgpt: how fast each uses that plan”
- estimate_coston 48 other servers
“Price a workload on 1 to 10 models at each one's cheapest listing: dollars per call, per day and per 30 days, and with cache tokens the saving the cache makes.”
Publisher declares: read-only yes · idempotent yes · open-world no
6 inputs, 3 required
modelsarrayrequired“1 to 10 model names”input_tokensintegerrequired“Prompt tokens per call”output_tokensintegerrequired“Answer tokens per call, including hidden thinking”cached_tokensinteger“How many of the prompt tokens are read from the cache”calls_per_daynumber“Calls per day”cache_write_tokensinteger“How many of the prompt tokens are written to the cache”
“Show one model's price history: every price and retirement date change since 2023 on every host, each with the LiteLLM change behind it, the chance of a price change, retirement or removal in the nex…”
Publisher declares: read-only yes · idempotent yes · open-world no
2 inputs, 1 required
modelstringrequired“A model name, for example claude-opus-5.5, or one listing such as bedrock/anthropic.claude-opus-5-5”datestring or null“A day as YYYY-MM-DD: each listing's prices that day and the change that set them”
- suggest_for_projecton 1 other server
“Suggest a model and effort level for a prompt or a described project: it guesses the kind of work and names the best value (the cheapest model the votes cannot tell apart from the top), the top rated…”
Publisher declares: read-only yes · idempotent yes · open-world no
3 inputs, 1 required
promptstringrequired“The project's starting prompt, or a description of the work”paystring“api: dollars; claude or chatgpt: compare within that plan”answerstring“Typical answer length”
- not_yet_pricedreads or searches
“List the models Arena has rated that LiteLLM's catalogue does not price yet, with how soon the catalogue usually prices a maker's models after Arena first shows them.”
Publisher declares: read-only yes · idempotent yes · open-world no
1 input
makerstring or null“Only this maker, for example meta or ibm”
- estimate_time
“Estimate how long one call and a whole job take, as a usual time and a slow day, from the user's own timed runs of that model called that way (kept by log_run).”
Publisher declares: read-only yes · idempotent yes · open-world no
7 inputs, 3 required
modelstringrequired“A model name, as the catalogue or Ollama names it”input_tokensintegerrequired“Prompt tokens per call”output_tokensintegerrequired“Answer tokens per call, including hidden thinking”callsinteger“How many calls the job makes”waystring“How the model is called”thinkingboolean“Thinking turned on”concurrencyinteger“Calls running at once”
- log_runcreates or changes datadescribed as changing data
“Record a timed run (model, tokens, seconds, how it was called), or every result of a promptfoo results file, in a file on this computer so estimate_time can learn from it.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
8 inputs
modelstring or null“The model that ran”input_tokensinteger or null“Prompt tokens of the call”output_tokensinteger or null“Answer tokens of the call, hidden thinking included”secondsnumber or null“How long the call took”waystring or null“How the model was called (default api; for a promptfoo file, read from each provider)”thinkingboolean“Thinking was on (a promptfoo result that counts thinking tokens is marked on by itself)”taskstring or null“The kind of work, if known”promptfoo_resultsstring or null“Path of a promptfoo results file (promptfoo eval -o results.json): every result becomes a run”
- forecast_job
“Estimate a whole job's time, cost and accuracy from a promptfoo run of a sample of it: for each model in the sample, the time as a usual time and a slow day, the cost at its cheapest listing next to …”
Publisher declares: read-only yes · idempotent yes · open-world no
6 inputs, 2 required
promptfoo_resultsstringrequired“Path of a promptfoo results file from a sample of the job (promptfoo eval --filter-sample 20 -o sample.json)”itemsintegerrequired“How many tests the whole job has”concurrencyinteger or null“Calls running at once in the whole job (default: as the sample ran)”waystring or null“How the models are called (default: read from each provider)”thinkingboolean“Thinking turned on”wrong_answer_costnumber or null“Dollars a wrong answer costs you to catch and fix; the pick then counts it”
- local_or_cloud
“Compare running an open model on a computer you buy with paying a cloud model per call: the cost a month each way, the month the computer pays for itself, and whether it keeps up with the load.”
Publisher declares: read-only yes · idempotent yes · open-world no
13 inputs, 6 required
local_modelstringrequired“The open model you would run at home, as Ollama names it, for example llama3.1:8b”cloud_modelsarrayrequired“1 to 5 cloud models to compare with”input_tokensintegerrequired“Prompt tokens per call”output_tokensintegerrequired“Answer tokens per call, including hidden thinking”calls_per_monthnumberrequired“Calls a month”hardware_pricenumberrequired“What the computer costs you, in dollars”wattsnumber or null“Power the computer draws while it answers, in watts”electricity_pricenumber or null“Your electricity price, dollars per kWh (default: EIA's average for homes)”statestring or null“A US state, for EIA's average there, for example Texas”monthsinteger“How many months to compare over”cached_tokensinteger“Prompt tokens read from the cloud model's cache”local_waystring“How the local model is called”thinkingboolean“Thinking turned on for the local model”
- price_my_usage
“Price the user's own past coding agent usage, from a ccusage or codeburn export, on every rated model: each session at the price of its day, the models that keep the rating and cost less, a 95% range…”
Publisher declares: read-only yes · idempotent yes · open-world no
5 inputs
exportstring or null“Path of a token export on this computer: `ccusage daily --json > f.json`, `ccusage session --json > f.json`, or `codeburn export -f json -o f.json`”mixarray or null“Instead of a file: token mixes as {model, date, input, output, cache_read, cache_write, session?}”taskstring or null“The kind of work the sessions were (default: codeburn's categories, else coding)”comparearray or null“Two models to test against each other on the same sessions”limitinteger“How many models to list in every_model (the cheapest first)”
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-23.
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
- Says what the tool does
- 100% of 11 tools
- Says what it returns
- 100% of 11 tools
- States limits, defaults or errors
- 91% of 11 tools
- Says when to use it
- 100% of 11 tools
- Items covered per tool
- 3.9 of 4 on average
Counted from the listing
- Parameters with a description
- 100% of 64
- Tools with a description
- 100% of 11
- Typical description length
- 419 characters
The tool set
Counted from the listing
- Tools
- 11
- Size of the list
- about 4,534 tokens for an agent to load (characters ÷ 4)
- Naming
- 11 of 11 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 11 of 11 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 PyPI package llmledger-mcp
Our sandbox started this package on 2026-10-23 (a read-only session: no tool was called).
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.
Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)
{
"mcpServers": {
"llmledger": {
"command": "uvx",
"args": [
"llmledger-mcp==0.2.0"
]
}
}
}Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"llmledger": {
"command": "uvx",
"args": [
"llmledger-mcp==0.2.0"
]
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"llmledger": {
"type": "stdio",
"command": "uvx",
"args": [
"llmledger-mcp==0.2.0"
]
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"llmledger","type":"stdio","command":"uvx","args":["llmledger-mcp==0.2.0"]}'Claude Code
claude mcp add --transport stdio llmledger -- uvx llmledger-mcp==0.2.0
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -- uvx llmledger-mcp==0.2.0
- This runs the publisher's code on your machine (uvx). Read its README first.
- 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.
Can it be installed, and is it up to date?
Version pin · advisories
Listed version
- Registry lists
- 0.2.0
- Latest stable
- 0.2.0
- Status
- current
- Withdrawn
- no
Source: pypi.org · 2026-10-23. About the version the registry lists; a manual install may resolve to a different one.
Dependency advisories
Counted in the full dependency tree as resolved on 2026-10-23 (OSV.dev). Bars share one scale. The package itself has no known vulnerability (OSV.dev).
Integrity, provenance, license
- Integrity
- sha256-30ab05f53c386362b…
- License
- MIT
Source: the package registry · 2026-10-23.
Usage
- Downloads
- 0 in the last month
Source: pypistats.org · 2026-10-23.
Does the registry listing match what we found?
Feature #6The 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 |
|---|---|---|---|
| Published package can be started | Started and answered | matches | our test · 2026-10-23 |
| Version 0.2.0 on PyPI | Exists and can be installed | matches | PyPI · 2026-10-23 |
| Repository github.com/pouriaetab/llmledger | Opens publicly | matches | api.github.com · 2026-10-23 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- io.github.pouriaetab
- GitHub owner
- a personal account (pouriaetab)
- Repository
- github.com/pouriaetab/llmledger
- Stars
- 0
- Repository age
- 0–30 days
- Last push
- 0–30 days ago
- Archived
- no
- Security policy
- none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)
Source: the registry entry and api.github.com · 2026-10-23; 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 rating7 of 8 record checks met · 1 does not apply
- #14,745 of 15,112 packages by monthly downloads, tied with 367 others
- 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.
- Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.
- MetPackage names its licence with a standard (SPDX) identifierMIT
- MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
- Does not applynpm package carries build provenance (attestation)PyPI packages have no npm-style attestation.
- MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. 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.github.pouriaetab/llmledger
Answered from the data aboveIs io.github.pouriaetab/llmledger safe to install?
We do not rate servers as safe or unsafe. 7 of its 8 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. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. 1 of its tools describes changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Has io.github.pouriaetab/llmledger been security tested?
Partly. 4 of the 13 checks that apply to it were exercised. We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security verdict is published before verification.
What can io.github.pouriaetab/llmledger do?
It lists 11 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search and create or change data. We did not call any tool, so this describes the text, not the behaviour.
Can io.github.pouriaetab/llmledger change or delete data?
1 of its tools says in its description that it creates, edits, deletes, sends or runs something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.
Does io.github.pouriaetab/llmledger publish a security policy?
We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.
Is the listed version current?
Yes. The registry lists 0.2.0, the latest stable release on PyPI.
Where is the source code of io.github.pouriaetab/llmledger?
In github.com/pouriaetab/llmledger, which opens publicly.
Found this page useful?
Anonymous · no sign-inA 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.vybenetwork/solana-mcp-vybeSolana MCP by Vybealso has tools that creates or changes data, reads or searchescompare with this one
- io.github.mnemox-ai/tradememory-protocolalso has tools that creates or changes data, reads or searchescompare with this one
- io.github.agent-next/polymarket-paper-traderPolymarket Paper Traderalso has tools that creates or changes data, reads or searchescompare with this one
- io.github.DeHor-Labs/mcp-fiscal-brasilMCP Fiscal Brasilalso has tools that creates or changes data, reads or searchescompare with this one
- io.github.codespar/mcp-khipualso has tools that creates or changes data, reads or searchescompare with this one
- io.github.nirholas/agentcore-payments-mcpthree.ws Agent Paymentsalso has tools that creates or changes data, reads or searchescompare with this one
Active servers whose topic is also “finance-and-payments” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. 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 (read-only run)
We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security score is given; a check we did not run is never counted as passed.
- 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 applicable
- Consent handling: not applicable
- Sign-in metadata: not applicable
4 exercised9 not run (reason given)5 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 4 of the 13 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.
- 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
- 3Real execution
real-executionCalls a tool and checks what really happens.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.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 package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy - 6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy - 7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.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 package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.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
- 14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable - 15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable - 16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable - 17Consent handling
confused-deputyChecks consent handling when one service acts for another.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
Source: our own test in an isolated sandbox, 2026-10-23, 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 the published package in an isolated sandbox (read-only mode)
- 3,566 msConnected after 0 redirects.
- Read the inventory: 11 tools, 1 resource, 1 prompt.
- 5,922 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.
“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.github.pouriaetab/llmledger: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.pouriaetab/llmledger
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
[](https://protocolprobe.com/mcp/servers/io.github.pouriaetab/llmledger)
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