logfire (pydantic/logfire) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it yet. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
B
Emerging
89/100

logfire

AI observability platform for production LLM and agent systems.

→ pydantic/logfire· listed on github_code

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

pydantic

Source: github_code

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

GitHub

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 1 credential: LOGFIRE_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configCODEX_HOME
configLOGFIRE_IGNORE_NO_CONFIG
configLOGFIRE_CONFIG_DIR
configPYTEST_CURRENT_TEST
configOTEL_INSTRUMENTATION_HTTP_CAPTURE_HEADERS_SERVER_REQUEST
configOTEL_INSTRUMENTATION_HTTP_CAPTURE_HEADERS_SERVER_RESPONSE
configAWS_LAMBDA_FUNCTION_NAME
configLOGFIRE_PYDANTIC_RECORD
configLOGFIRE_GATEWAY_URL
configLOGFIRE_BASE_URL
configPYTEST_VERSION
🔐 secretLOGFIRE_TOKEN
configLOGFIRE_SERVICE_NAME
configGITHUB_ACTIONS
configGITHUB_WORKFLOW
configGITHUB_REF
configGITHUB_SHA
configGITHUB_RUN_ID
configGITLAB_CI
configJENKINS_URL
configGIT_BRANCH
configGIT_COMMIT
configBUILD_NUMBER
configBUILD_URL
configGITHUB_SERVER_URL
configGITHUB_REPOSITORY
configTRACEPARENT
configTRACESTATE
configPYTEST_XDIST_WORKER
configPYTEST_XDIST_WORKER_COUNT
// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/pydantic/logfire)](https://m8ven.ai/mcp/pydantic/logfire)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 26e06cad443fec91e26b340766db288ad5c58738
code hash: 4b57d2f97c640d2e474ad7014cf0f3f1665f3dae8d103f5dce72cc63d2237d8f
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client