MCP servers › io.github.Siddhant-K-code › agent-trace
MCP server · registry snapshot 2026-11-19 · last checked 2026-11-19
agent-trace MCP server
Registry name io.github.Siddhant-K-code/agent-trace
agent-strace — the publisher's title
by Siddhant-K-code · GitHub account (the registry's namespace rule)repository: same ownerSource ↗PyPI ↗Website ↗
Query recorded AI agent sessions: events, summaries, diffs, health, skills, PR reviewability. — the publisher's description
Summary
io.github.Siddhant-K-code/agent-trace is a local MCP server listed in the official MCP registry at version 0.117.0, under the namespace of the GitHub account Siddhant-K-code. Its linked repository, github.com/Siddhant-K-code/agent-trace, belongs to the same GitHub account.
Record checks
8 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
- 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
- #595 of 20,610 packages by monthly downloads
- #935 of 28,859 repositories by GitHub stars, tied with 6 others
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it
Key facts
- Runs
- local package
- Transport
- standard input/output
- Your own values
- none declared (not a guarantee)
- Package
- PyPI · listed version current
- License
- MIT
- Dependencies
- no known high or critical advisories
- Repository
- public
- Last tested
- not tested
Tool list
Not read: It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's. So there is no tool-list size and no result from the three APIs.
How fresh this is
- Live-tested
- no
- Last tested
- not tested
- Latest version
- 0.117.0, published 2026-11-19 (registry, as of the 2026-11-19 snapshot)
- First listed version
- 2026-11-09 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 25 versions listed, 2026-11-09 to 2026-11-19; 25 in the 90 days before the 2026-11-19 snapshot.(versions still listed in the registry only)
Most recent 12 versions
0.117.0· 2026-11-190.116.0· 2026-11-180.115.2· 2026-11-180.115.1· 2026-11-170.115.0· 2026-11-170.114.3· 2026-11-170.114.2· 2026-11-170.114.1· 2026-11-170.114.0· 2026-11-170.113.1· 2026-11-160.113.0· 2026-11-160.112.1· 2026-11-16
- Registry data
- snapshot 2026-11-19
- Package and repository
- checked 2026-11-19
Dead or stale signals
None found in the records we hold
Looked for and not found: deprecated in the registry; 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
Version 0.116.0 (published 2026-11-18) → 0.117.0 (published 2026-11-19), between the registry lists of 2026-11-18 and 2026-11-19.
The publisher’s GitHub release note for v0.117.0, published 2026-11-19.
Read the release note (the publisher’s text, shown as plain text, cut at 4,000 characters)
The VS Code extension fixes #478 and #480 shipped separately in `vscode-v0.5.2` (#486). Core v0.117.0 does not change the extension, which stays at version 0.5.2. ## Fixes - `record` (the MCP stdio proxy) now exits when the agent closes its stdin. It first waits for the server's last replies and relays and traces them. Before, `record` could hang and drop replies. (#485) - `record` stops the server, ends the session and exits 143 on SIGTERM or 130 on SIGINT. Before, the server kept running and the session had no end time. (#485) - `record` reports a server that cannot start, records the error, ends the session and exits 127 when the command is not found, 126 when it cannot run, or 1. It no longer aborts with exit 134 when the server exits while the agent still holds stdin open. A deleted `--parent` session no longer makes `record` lose its end time. (#485) - `record` now stops the MCP server's child processes too, when it stops the server and when the server exits and leaves them running. On Windows every child is in a job object. On POSIX it is best effort and never signals unrelated processes. (#487) - `record` ends the session cleanly in every case: `session_end` is always the last event, its counts match the trace, and nothing is written to the agent after it. Server output still not relayed 5 seconds after the server exits is cut short, and a write the agent does not take within 5 seconds is cancelled. Each is recorded as an `error`, and `session_end` gets `output_truncated`. A reply that is cut short can be in the trace without reaching the agent. A SIGTERM or SIGINT before the server starts ends the session without starting it. (#487) - `auto` now passes SIGTERM, SIGINT and SIGHUP on to the command and its whole process group, waits for them to exit, and removes its temporary hook directory. Before, SIGTERM or SIGHUP left the directory behind and the command running. Ctrl-C in a shell loop that runs `auto` still stops the loop. (#493) - CrewAI, OpenAI Agents and Strands runs are now each recorded as their own session, closed with session_end, duration and tool, LLM and error counts. Before, sessions never ended and later runs were added to the same session. Overlapping runs, including runs in other processes, no longer overwrite each other's session. (#492) - Tool results and errors now link to their tool call in CrewAI, OpenAI Agents, Strands and LangChain. OpenAI Agents tool calls are recorded again on openai-agents 0.25 or later. `uninstrument_openai_agents` now removes its patches. (#492) - Python SDK integrations (OpenAI, Anthropic, LiteLLM) record a model call ended by KeyboardInterrupt, SystemExit or task cancellation as a cancelled response, so its request is always closed. This covers streams too. (#488) - `@trace_tool` and `@trace_llm_call` now trace `async def` functions. They await the call and record its result, error and duration. Before, they recorded the coroutine object with a duration near 0 ms and missed errors raised inside it. (#479) - `start_session()` now ends the thread's active session before it starts a new one. Before, the first session was left open with no end time. (#479) - `agent-strace import` no longer duplicates events when the same Claude Code JSONL log is imported again. It now writes nothing, prints that the session is already imported, and exits 0. A log that fails part way no longer leaves a partial session. (#489) - `a2a` tree shows a sub-agent that one parent called more than once as a single node with a delegation count, instead of a false `[cycle]`, and OTLP export no longer emits duplicate span IDs. Linking a sub-session sets its depth to its parent's depth plus one and no longer loses meta updates the sub-agent writes at the same time. `record-http` keeps a parent link and depth that another proxy wrote while it ran. (#491) - `token-budget` and `watch --max-context-pct` now measure how full the context window is on each request: that request's input tokens over the model's c
Source: the official MCP Registry list on 2026-11-18 and on 2026-11-19; release notes from the GitHub Releases API, checked 2026-11-19.
What it is
How do I add it to my client?
Config from the registry entry
From the PyPI package agent-strace
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": {
"agent-trace": {
"command": "uvx",
"args": [
"agent-strace==0.117.0",
"mcp"
]
}
}
}Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"agent-trace": {
"command": "uvx",
"args": [
"agent-strace==0.117.0",
"mcp"
]
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"agent-trace": {
"type": "stdio",
"command": "uvx",
"args": [
"agent-strace==0.117.0",
"mcp"
]
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"agent-trace","type":"stdio","command":"uvx","args":["agent-strace==0.117.0","mcp"]}'Claude Code
claude mcp add --transport stdio agent-trace -- uvx agent-strace==0.117.0 mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"agent-trace": {
"command": "uvx",
"args": [
"agent-strace==0.117.0",
"mcp"
],
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"agent-trace": {
"command": "uvx",
"args": [
"agent-strace==0.117.0",
"mcp"
]
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.agent-trace] command = "uvx" args = ["agent-strace==0.117.0", "mcp"]
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"agent-trace": {
"command": "uvx",
"args": [
"agent-strace==0.117.0",
"mcp"
]
}
}
}Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -- uvx agent-strace==0.117.0 mcp
- Arguments are written as the registry entry gives them; a named one as “--name value”, the form the registry documentation shows.
- Optional settings the entry also lists (left out above): AGENT_TRACE_DIR.
- 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; 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.
Can it be installed, and is it up to date?
Version pin · advisories
Listed version
- Registry lists
- 0.117.0
- Latest stable
- 0.117.0
- Status
- current
- Withdrawn
- no
Source: pypi.org · 2026-11-19. 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-11-19 (OSV.dev; each bar counts advisories). Bars share one scale. The package itself has no known vulnerability (OSV.dev).
Integrity, provenance, license
- Integrity
- sha256-e3df34a0625927c72…
- License
- MIT
Source: the package registry · 2026-11-19.
Usage
- Downloads
- 5,245 in the last month
Source: pypistats.org · 2026-11-19.
What do the published files and outside lists say?
Read as text · nothing run · no tool called
Package files
- Python version and wheels (PyPI). Needs Python 3.10 or later (requires_python
>=3.10). Source: pypi.org/pypi/agent-strace/0.117.0/json · read 2026-11-19. - Build workflow. No build provenance published for this version. Source: pypi.org/integrity/agent-strace/0.117.0/agent_strace-0.117.0-py3-none-any.whl/provenance · read 2026-11-19.
Registry entry
- Same package in other registry entries. No other registry entry lists this entry's npm or PyPI package at a newer version. Source: own registry snapshot · read 2026-11-19.
Outside lists
- CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-19. This product uses the NVD API but is not endorsed or certified by the NVD.
- GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-19. GitHub Advisory Database, CC BY 4.0
- Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-19. Source: read 2026-11-19.
- Cline marketplace. Not in the Cline marketplace on 2026-11-19. Source: read 2026-11-19.
Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read
Does the registry listing match what we found?
Feature #6The 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 says | We found | Result | Source · date |
|---|---|---|---|
| Version 0.117.0 on PyPI | Exists and can be installed | matches | PyPI · 2026-11-19 |
| Repository github.com/Siddhant-K-code/agent-trace | Opens publicly | matches | api.github.com · 2026-11-19 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- io.github.Siddhant-K-code
- GitHub owner
- a personal account (Siddhant-K-code)
- Repository
- github.com/Siddhant-K-code/agent-trace
- Stars
- 108
- Repository age
- 181–365 days
- Last push
- 0–30 days ago
- Archived
- no
- Security policy
- SECURITY.md
Source: the registry entry and api.github.com · 2026-11-19; security policy read from GitHub · 2026-11-09.
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 rating8 of 8 record checks met · 1 does not apply
- #595 of 20,610 packages by monthly downloads
- #935 of 28,859 repositories by GitHub stars, tied with 6 others
- 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.
- 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-11-19 (security policy 2026-11-09). 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, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral
Common questions about io.github.Siddhant-K-code/agent-trace
Answered from the data aboveWho publishes io.github.Siddhant-K-code/agent-trace?
The registry ties the namespace io.github.Siddhant-K-code to the GitHub account Siddhant-K-code; only its owner can publish under it. Its linked repository, github.com/Siddhant-K-code/agent-trace, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.
Is io.github.Siddhant-K-code/agent-trace safe to install?
We do not rate servers as safe or unsafe. 8 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. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Has io.github.Siddhant-K-code/agent-trace been security tested?
No. It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's.
Does io.github.Siddhant-K-code/agent-trace publish a security policy?
Yes: its repository has a public security policy (github.com/siddhant-k-code/agent-trace/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.
Is the listed version current?
Yes. The registry lists 0.117.0, the latest stable release on PyPI.
Where is the source code of io.github.Siddhant-K-code/agent-trace?
In github.com/Siddhant-K-code/agent-trace, 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.
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
Has it been tested?
Feature #1It could be started, but has not been tested; we call no server's tools for anything we publish, except for a server whose operator has claimed it and given permission (that server's page says so). This is our limit, not the server's. — our limit
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.Siddhant-K-code/agent-trace: MCP server record.” Data checked 2026-11-19. https://protocolprobe.com/mcp/servers/io.github.Siddhant-K-code/agent-trace
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.Siddhant-K-code/agent-trace)
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, except for a server whose operator has claimed it and given permission (that server's page says so).
Write to hello@protocolprobe.com · corrections log · methodology