MCP servers › io.github.sepehr071 › toolsmelt
MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23
io.github.sepehr071/toolsmelt
Curated MCP tools from OpenAPI, websites, apps, Postman, cURL or SQL; your agent designs them. — the publisher's description
Summary
io.github.sepehr071/toolsmelt is a local MCP server listed in the official MCP registry at version 0.8.0. On 2026-10-23 ProtocolProbe started its published package in an isolated sandbox in read-only mode and read its inventory: 19 tools, 0 resources and 0 prompts.
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
- Not ranked by downloads: no download figure available
- #2,573 of 22,952 repositories by GitHub stars, tied with 148 others
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
- 19
- Described as changing data
- 14 of 19 toolsAI-classified
- Mainly works on
- files and code on the machine it runs on; accounts and data in outside web servicesAI-classified
- Topic
- developer-toolsAI-classified
- Last tested
- 2026-10-23
Worth knowing before you connect it
- 14 tools are described as changing something (smith_inspect, smith_app_android, smith_app_js, …): our AI model's reading of the descriptions, not something we tested. We did not call them.
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.8.0, published 2026-10-22 (registry, as of the 2026-10-23 snapshot)
- First listed version
- 2026-10-22 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 2 versions listed, all on 2026-10-22; 2 in the 90 days before the 2026-10-23 snapshot.(versions still listed in the registry only)
Most recent 2 versions
0.8.0· 2026-10-220.7.0· 2026-10-22
- 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.8.0 (published 2026-10-22).
Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.
What it is
What does this server offer?
Observed inventoryWhat it mainly works on, as our AI model read its tool descriptions: files and code on the machine it runs on; accounts and data in outside web services.
14 of 19 tools are described as changing something (creating, editing, deleting, sending or running).
“Return the rules for designing the tools of an MCP server (the plan.yaml format).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
Takes no inputs.
“Read an OpenAPI file or HAR and write source.json and digest.md into the workdir.”
Publisher declares: read-only no · destructive yes · open-world yes
4 inputs, 1 required
sourcestringrequired“OpenAPI/Swagger file or HAR, as an absolute path or an http(s) URL.”workdirstring“Absolute directory for source.json, digest.md and plan.yaml.”hostsarray or null“HAR only: keep traffic to these hosts, e.g.”budgetinteger“Maximum digest size in characters.”
“Read the HTTP interface an Android app declares (through the jadx CLI or REA's JADX jar) into source.json, for the user's own or an authorized app.”
Publisher declares: read-only no · destructive yes · open-world yes
6 inputs
apkstring or null“Absolute path of the APK on this machine.”class_namestring or null“Decompiled Retrofit interface class; omit to list candidate classes.”base_urlstring“The app's API base URL, e.g.”workdirstring“Absolute directory for source.json and digest.md.”source_filestring or null“Absolute path of a .java class already decompiled by any tool; skips the jar.”jadx_jarstring or null“REA's JADX MCP jar; default: `jadx` on PATH, else $REA_JADX_MCP_JAR.”
“Read the HTTP calls an Electron/JavaScript app makes out of its own shipped code, for the user's own or an authorized app.”
Publisher declares: read-only no · destructive yes · open-world yes
3 inputs, 1 required
pathstringrequired“Absolute path of the app directory, its app.asar, or one .js/.ts/.map file.”base_urlstring“The app's API base URL, e.g.”workdirstring“Absolute directory for source.json and digest.md.”
“Guide recording a desktop program's own traffic, then import the HAR, for the user's own or an authorized program.”
Publisher declares: read-only no · destructive yes · open-world yes
5 inputs
harstring or null“Absolute path of the HAR the user's own mitmdump wrote; omit to get the steps.”hostsarray or null“Keep traffic to these hosts only.”workdirstring“Absolute directory for source.json and digest.md.”portinteger“Proxy port used in the steps.”forceboolean“Overwrite an existing source.json.”
“Write a heuristic starting <workdir>/plan.yaml from source.json.”
Publisher declares: read-only no · destructive yes · open-world yes
3 inputs, 1 required
workdirstringrequired“Absolute workdir that smith_inspect wrote source.json into.”namestring or null“Project name, e.g.”forceboolean“Overwrite an existing plan.yaml (loses your edits).”
“Check plan.yaml against the design rules and return its errors and warnings.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
2 inputs
workdirstring or null“Absolute workdir holding plan.yaml (and source.json).”plan_pathstring or null“Absolute path of a plan file, if not <workdir>/plan.yaml.”
“Validate plan.yaml and, if it has no errors, write the server project.”
Publisher declares: read-only no · destructive yes · open-world yes
3 inputs, 1 required
workdirstringrequired“Absolute workdir holding plan.yaml (and source.json).”outstring or null“Absolute output directory.”forceboolean“Write into an existing output directory.”
“Register a generated server with the user's coding agents so it runs as a normal MCP server.”
Publisher declares: read-only no · destructive yes · open-world yes
6 inputs, 1 required
projectstringrequired“Absolute path of a project written by smith_generate.”agentsarray or null“Agents to register with: claude, codex, cursor, gemini.”removeboolean“Remove the project's entry instead.”forceboolean“Replace an entry of the same name that runs something else.”pypiboolean“Run the released package (uvx name@version), not the folder.”dry_runboolean“Only return the planned changes; false applies them.”
“Call unverified GET endpoints live with the user's own credentials and store scrubbed example responses.”
Publisher declares: read-only no · destructive yes · open-world yes
3 inputs, 1 required
workdirstringrequired“Absolute workdir holding source.json.”limitinteger“Most endpoints to probe.”writesboolean“Also call non-GET endpoints on the live API.”
“Call every tool of a generated project against the live API with its example arguments.”
Publisher declares: read-only no · destructive yes · open-world yes
2 inputs, 1 required
projectstringrequired“Absolute path of a generated project directory.”writesboolean“Also call tools that change data on the live API.”
“Start recording the API calls of the shared Chrome (opened with `toolsmelt browser`) into a HAR.”
Publisher declares: read-only no · destructive yes · open-world yes
2 inputs, 2 required
namestringrequired“Short name for this recording, e.g.”hostsarrayrequired“Record only these hosts and their subdomains, e.g.”
Show 7 more tools
“Stop the recording and write capture.har; then inspect it with smith_inspect.”
Publisher declares: read-only no · destructive yes · open-world yes
1 input, 1 required
namestringrequired“The name given to smith_record_start.”
“Validate plan.yaml and, if it has no errors, add its tools to this server right now.”
Publisher declares: read-only no · destructive yes · open-world yes
2 inputs, 1 required
workdirstringrequired“Absolute workdir holding plan.yaml (and source.json).”namestring or null“Connection name.”
“Remove a connection's tools from this server and forget the connection.”
Publisher declares: read-only no · destructive yes · open-world yes
1 input, 1 required
namestringrequired“Connection name, from smith_connections.”
“Return who is signed in to a connection, or how the user signs in (a link for signin auth).”
Publisher declares: read-only no · destructive yes · open-world yes
2 inputs, 1 required
connectionstringrequired“Connection name, from smith_connections.”againboolean“Sign in again, e.g.”
“List the connected sites: tools, auth type, and whether each loaded.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
Takes no inputs.
“List the tools of one connection with their descriptions and input schemas, plus the plan's instructions.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
1 input, 1 required
connectionstringrequired“Connection name, from smith_connections.”
“Call a read-only tool of a connection by name, for clients that do not refresh their tool list.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
3 inputs, 2 required
connectionstringrequired“Connection name, from smith_connections.”toolstringrequired“Tool name, from smith_tools.”argsobject or null“The tool's arguments.”
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 19 tools
- Says what it returns
- 93% of 15 tools
- States limits, defaults or errors
- 11% of 18 tools
- Says when to use it
- 100% of 19 tools
- Items covered per tool
- 3.1 of 4 on average
Counted from the listing
- Parameters with a description
- 100% of 49
- Tools with a description
- 100% of 19
- Typical description length
- 228 characters
The tool set
Counted from the listing
- Tools
- 19
- Size of the list
- about 3,616 tokens for an agent to load (characters ÷ 4)
- Naming
- 19 of 19 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 19 of 19 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 toolsmelt
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": {
"toolsmelt": {
"command": "uvx",
"args": [
"toolsmelt==0.8.0",
"mcp"
]
}
}
}Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"toolsmelt": {
"command": "uvx",
"args": [
"toolsmelt==0.8.0",
"mcp"
]
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"toolsmelt": {
"type": "stdio",
"command": "uvx",
"args": [
"toolsmelt==0.8.0",
"mcp"
]
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"toolsmelt","type":"stdio","command":"uvx","args":["toolsmelt==0.8.0","mcp"]}'Claude Code
claude mcp add --transport stdio toolsmelt -- uvx toolsmelt==0.8.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 toolsmelt==0.8.0 mcp
- Arguments are written as the registry entry gives them; a named one as “--name value”, the form the registry documentation shows.
- 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.8.0
- Latest stable
- 0.8.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-6a13c4e267389430d…
- License
- MIT
Source: the package registry · 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.8.0 on PyPI | Exists and can be installed | matches | PyPI · 2026-10-23 |
| Repository github.com/sepehr071/toolsmelt | 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.sepehr071 · 38 servers
- GitHub owner
- a personal account (sepehr071)
- Repository
- github.com/sepehr071/toolsmelt
- Stars
- 10
- 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.
Same tools as other registry entries
Tool lists read · names comparedIts 19 tools have exactly the same names as the tools of 1 other registry entry (all published under the same registry namespace). Their tool descriptions differ in places.
This can be one publisher's family of servers or one template reused under many names. It is a fact about the published tool lists, not a judgement of the publisher and not a safety finding; we compared tool names, not code.
Shared tool names (12 of 19 shown):
smith_app_androidsmith_app_desktopsmith_app_jssmith_callsmith_checksmith_connectsmith_connectionssmith_disconnectsmith_draftsmith_generatesmith_guidesmith_inspectThe other entries
All groups of servers with identical tool lists
Source: our read-only reads of each server's tool list · 2026-10-23. No tool was called.
Choosing
Record checks
Public records · not a safety rating7 of 8 record checks met · 1 does not apply
- Not ranked by downloads: no download figure available
- #2,573 of 22,952 repositories by GitHub stars, tied with 148 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.
- 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.sepehr071/toolsmelt
Answered from the data aboveIs io.github.sepehr071/toolsmelt 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. 14 of its tools describe 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.sepehr071/toolsmelt been security tested?
Partly. 2 of the 12 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.sepehr071/toolsmelt do?
It lists 19 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, create or change data, delete and manage infrastructure. We did not call any tool, so this describes the text, not the behaviour.
Can io.github.sepehr071/toolsmelt change or delete data?
14 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.
Does io.github.sepehr071/toolsmelt 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.8.0, the latest stable release on PyPI.
Where is the source code of io.github.sepehr071/toolsmelt?
In github.com/sepehr071/toolsmelt, 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.A9T9/uivision-mcpUi.Vision MCPalso has tools that creates or changes data, deletes, manages infrastructure, reads or searchescompare with this one
- io.github.tugcantopaloglu/godot-mcpGodot MCPalso has tools that creates or changes data, deletes, manages infrastructure, reads or searchescompare with this one
- io.github.codegraph-ai/codegraphalso has tools that creates or changes data, deletes, manages infrastructure, reads or searchescompare with this one
- com.mcparmory/codacyalso has tools that creates or changes data, deletes, manages infrastructure, reads or searchescompare with this one
- com.mcparmory/gitlabalso has tools that creates or changes data, deletes, manages infrastructure, reads or searchescompare with this one
- io.github.sapiom/mcpalso has tools that creates or changes data, deletes, manages infrastructure, reads or searchescompare with this one
Active servers whose topic is also “developer-tools” 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: not run · nothing to check it against
- Fake assistant turns: not applicable
- Token passthrough: not applicable
- Token audience: not applicable
- Sign-in redirect: not applicable
- Consent handling: not applicable
- Sign-in metadata: not applicable
2 exercised10 not run (reason given)6 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 12 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
- 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 - 12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
- 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable - 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)
- 1,669 msConnected after 0 redirects.
- Read the inventory: 19 tools, 0 resources, 0 prompts.
- 2,177 msFinished: 2 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.sepehr071/toolsmelt: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.sepehr071/toolsmelt
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.sepehr071/toolsmelt)
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