MCP servers › io.github.aldoogando03-bit › mcp-tracer
MCP server · registry snapshot 2026-11-12 · last tested 2026-11-20
mcp-tracer MCP server
Registry name io.github.aldoogando03-bit/mcp-tracer
by aldoogando03-bit · GitHub account (the registry's namespace rule)repository: same ownerSource ↗npm ↗
Design Cisco Packet Tracer topologies with AI agents and generate ready-to-run PTBuilder scripts. — the publisher's description
Summary
io.github.aldoogando03-bit/mcp-tracer is a local MCP server listed in the official MCP registry at version 0.1.1, under the namespace of the GitHub account aldoogando03-bit. Its linked repository, github.com/aldoogando03-bit/mcp-tracer, belongs to the same GitHub account. On 2026-11-20 ProtocolProbe started its published package in an isolated sandbox in read-only mode and read its inventory: 15 tools, 1 resource and 4 prompts.
Record checks
- 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 met: npm package carries build provenance (attestation)
- met: No known critical or high advisory in the package or its dependencies
- #7,607 of 20,725 packages by monthly downloads, tied with 14 others
- Not ranked by stars: 1 star (ranked from 10)
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
- npm · listed version current
- License
- MIT
- Dependencies
- no known high or critical advisories
- Repository
- public
- Tools
- 15
- Last tested
- 2026-11-20
Tool list at the three APIs
Not sent yet for this version (0.1.1).
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-11-20
- Mode
- read-only (no tool calls)
- Latest version
- 0.1.1, published 2026-11-06 (registry, as of the 2026-11-12 snapshot)
- First listed version
- 2026-11-06 (earliest version still in the registry; older removed versions would be earlier)
- Registry data
- snapshot 2026-11-12
- Package and repository
- checked 2026-11-12
- 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; 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-11-06, listed on 2026-11-07 with version 0.1.1 (published 2026-11-06).
Source: the official MCP Registry list on 2026-11-06 and on 2026-11-07.
What it is
What does this server offer?
Observed inventoryNone of its 15 tools are described as changing anything. For 15 the reading was uncertain, so no mark is shown.
- add_deviceon 1 other server
“Add a device to the topology.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
4 inputs, 2 required
namestringrequired“Unique device name, e.g.”modelstringrequired“PTBuilder model key, e.g.”xnumber“X coordinate on the Packet Tracer logical workspace, -100000 to 100000.”ynumber“Y coordinate on the Packet Tracer logical workspace, -100000 to 100000.”
- add_linkon 2 other servers
“Connect two device ports with a cable.”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
5 inputs, 4 required
dev1stringrequired“Device name, e.g.”port1stringrequired“Interface name, e.g.”dev2stringrequired“Device name, e.g.”port2stringrequired“Interface name, e.g.”cablestring“Cable type.”
- remove_deviceon 1 other server
“Remove a device together with its links, IOS commands and IP configuration.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
1 input, 1 required
namestringrequired“Device name, e.g.”
- remove_link
“Remove the link that uses the given device port (a port belongs to at most one link).”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
2 inputs, 2 required
devicestringrequired“Device name, e.g.”portstringrequired“Interface name, e.g.”
- rename_device
“Rename a device; its links, IOS commands and IP configuration follow.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
2 inputs, 2 required
namestringrequired“Device name, e.g.”new_namestringrequired“New unique device name, e.g.”
- configure_device
“Add IOS configuration commands to a router, switch or multilayer switch (not PCs, servers, ASAs, access points or wireless routers).”
Publisher declares: read-only no · destructive no · idempotent no · open-world no
3 inputs, 2 required
namestringrequired“Device name, e.g.”ios_commandsarrayrequired“IOS commands in global configuration mode, one per item, e.g.”replaceboolean“true = discard this device's previous commands first.”
- configure_pc
“Set the IPv4 configuration of a host: PC-PT and Server-PT (Laptop-PT and Printer-PT are accepted but unverified).”
Publisher declares: read-only no · destructive no · idempotent yes · open-world no
6 inputs, 1 required
namestringrequired“Device name, e.g.”dhcpboolean“true = obtain the address by DHCP (ip/mask/gateway are ignored).”ipstring“IPv4 address, e.g.”maskstring“Subnet mask, e.g.”gatewaystring“Default gateway IPv4 address.”dnsstring“DNS server IPv4 address (kept with DHCP too).”
- build_topology
“Replace the whole topology in one call.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
4 inputs, 1 required
devicesarrayrequired“Devices to create (at most 500).”linksarray“Links between device ports (at most 2000).”iosarray“IOS commands per router/switch (global configuration mode).”pcsarray“Host IP configurations (as configure_pc).”
- get_topologyon 2 other servers
“Return the current topology as JSON: devices (with the position that will be emitted; autoPlaced: true when the auto layout computed it), links (with the cable that will be emitted), IOS commands and…”
Publisher declares: read-only yes · open-world no
Takes no inputs.
- validate_configon 11 other servers
“Check the topology before generate_script.”
Publisher declares: read-only yes · open-world no
Takes no inputs.
- generate_scripton 3 other servers
“Generate the PTBuilder JavaScript for the current topology.”
Publisher declares: read-only yes · open-world no
1 input
forceboolean“Generate even if validation reports errors.”
- reset_topology
“Delete every device, link and configuration.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
Takes no inputs.
Show 3 more tools
- save_topology
“Save the current topology (devices, links, IOS commands, host IP configurations) to a JSON file that load_topology can read back.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
2 inputs, 1 required
pathstringrequired“File to write, e.g.”overwriteboolean“true = replace the file if it already exists.”
- load_topology
“Replace the current topology with one read from a file written by save_topology (a bare get_topology JSON object is accepted too).”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
1 input, 1 required
pathstringrequired“File to read.”
- export_scripton 2 other servers
“Write the PTBuilder script for the current topology to a file, for users who prefer a file to copying from chat.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
3 inputs, 1 required
pathstringrequired“File to write, e.g.”overwriteboolean“true = replace the file if it already exists.”forceboolean“Export even if validation reports errors.”
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-11-20; remote servers are read the day they appear and again about every 30 days; package servers at the monthly refresh.
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 34
- Tools with a description
- 100% of 15
- Typical description length
- 430 characters
The tool set
Counted from the listing
- Tools
- 15
- Size of the list
- about 4,884 tokens for an agent to load (characters ÷ 4)
- Naming
- 15 of 15 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 0 of 15 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 npm package mcp-tracer
Our sandbox started this package on 2026-11-20 (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": {
"mcp-tracer": {
"command": "npx",
"args": [
"-y",
"mcp-tracer@0.1.1"
]
}
}
}Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"mcp-tracer": {
"command": "npx",
"args": [
"-y",
"mcp-tracer@0.1.1"
]
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"mcp-tracer": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"mcp-tracer@0.1.1"
]
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"mcp-tracer","type":"stdio","command":"npx","args":["-y","mcp-tracer@0.1.1"]}'Claude Code
claude mcp add --transport stdio mcp-tracer -- npx -y mcp-tracer@0.1.1
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"mcp-tracer": {
"command": "npx",
"args": [
"-y",
"mcp-tracer@0.1.1"
],
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"mcp-tracer": {
"command": "npx",
"args": [
"-y",
"mcp-tracer@0.1.1"
]
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.mcp-tracer] command = "npx" args = ["-y", "mcp-tracer@0.1.1"]
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"mcp-tracer": {
"command": "npx",
"args": [
"-y",
"mcp-tracer@0.1.1"
]
}
}
}Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -- npx -y mcp-tracer@0.1.1
- This runs the publisher's code on your machine (npx). 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.1.1
- Latest stable
- 0.1.1
- Status
- current
- Withdrawn
- no
Source: registry.npmjs.org · 2026-11-12; new versions read the day they appear; the rest re-read about every 30 days. 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-07 (npm audit; each bar counts packages with an advisory, not advisories). Bars share one scale. The package itself has no known vulnerability (OSV.dev).
Integrity, provenance, license
- Integrity
- sha512-Vp7WVzzE/FeacXOC7…
- Signature
- signed
- License
- MIT
Source: the package registry · 2026-11-12.
Usage
- Downloads
- 568 in the last month
Source: api.npmjs.org · 2026-11-12.
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 |
|---|---|---|---|
| Published package can be started | Started and answered | matches | our test · 2026-11-20 |
| Version 0.1.1 on npm | Exists and can be installed | matches | npm · 2026-11-12 |
| Repository github.com/aldoogando03-bit/mcp-tracer | Opens publicly | matches | api.github.com · 2026-11-12 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- io.github.aldoogando03-bit
- GitHub owner
- a personal account (aldoogando03-bit)
- Build record
- signed
- Repository
- github.com/aldoogando03-bit/mcp-tracer
- Stars
- 1
- Repository age
- 181–365 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-11-12; security policy read from GitHub · 2026-11-07; read when the server is listed, then about every 30 days; an operator can ask for an earlier re-read.
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 9 record checks met
- #7,607 of 20,725 packages by monthly downloads, tied with 14 others
- Not ranked by stars: 1 star (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.What changes this check: GitHub's documentation describes adding a SECURITY.md from the repository's security settings: under Reporting, Security policy, Start setup. GitHub: adding a security policy
- 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.
- Not metnpm package carries build provenance (attestation)Signed by npm, but no build attestation.What changes this check: npm's documentation describes publishing with provenance from a cloud-hosted runner of a supported CI/CD provider, using npm CLI 9.5.0 or newer and npm publish --provenance. npm: generating provenance statements
- 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-12 (security policy 2026-11-07). 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.aldoogando03-bit/mcp-tracer
Answered from the data aboveWho publishes io.github.aldoogando03-bit/mcp-tracer?
The registry ties the namespace io.github.aldoogando03-bit to the GitHub account aldoogando03-bit; only its owner can publish under it. Its linked repository, github.com/aldoogando03-bit/mcp-tracer, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.
Is io.github.aldoogando03-bit/mcp-tracer safe to install?
We do not rate servers as safe or unsafe. 7 of its 9 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.aldoogando03-bit/mcp-tracer 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. ProtocolProbe publishes no security verdict for a named server.
Does io.github.aldoogando03-bit/mcp-tracer 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.1.1, the latest stable release on npm.
Where is the source code of io.github.aldoogando03-bit/mcp-tracer?
In github.com/aldoogando03-bit/mcp-tracer, 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
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. These 18 checks are separate from the record checks at the top of this page, which read public records only.
- 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-11-20, 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,321 msConnected after 0 redirects.
- Read the inventory: 15 tools, 1 resource, 4 prompts.
- 4,278 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. How often each is read again: methodology.
“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.aldoogando03-bit/mcp-tracer: MCP server record.” Data checked 2026-11-20. https://protocolprobe.com/mcp/servers/io.github.aldoogando03-bit/mcp-tracer
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.aldoogando03-bit/mcp-tracer)
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