MCP servers › com.scriptmasterlabs › sml-x402-agent-wallet
MCP server · registry snapshot 2026-11-07 · last checked 2026-11-07
sml-x402-agent-wallet MCP server
Registry name com.scriptmasterlabs/sml-x402-agent-wallet
by scriptmasterlabs.com · domain (the registry's namespace rule)Source ↗
Agent payer wallet: trust pre-flight, spend leash, Verdict step-up, evidence log. — the publisher's description
Summary
com.scriptmasterlabs/sml-x402-agent-wallet is an MCP server listed in the official MCP registry at version 1.1.0, under the namespace of the domain scriptmasterlabs.com. Its linked repository is gitlab.com/script-master-labs-llc-group/x402-kit.
Record checks
0 of 1 record check met · 7 do not apply · 1 not checked
- not met: Registry entry is active and says how to run it
- not checked: Source repository link opens
- not applicable: Repository is not archived
- not applicable: Code pushed to the repository in the 90 days before our check
- not applicable: Repository publishes a security policy (SECURITY.md)
- not applicable: Package names its licence with a standard (SPDX) identifier
- not applicable: The version the registry lists can be installed and is not withdrawn
- not applicable: npm package carries build provenance (attestation)
- not applicable: No known critical or high advisory in the package or its dependencies
- Not ranked by downloads: not an npm or PyPI package
- Not ranked by stars: no public GitHub repository
From public records, not a safety rating. Each check with its reason
Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it
Key facts
- Last tested
- not tested
Tool list
Not read: The registry entry declares no package and no remote endpoint, so there is nothing to run. 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
- 1.1.0, published 2026-11-07 (registry, as of the 2026-11-07 snapshot)
- First listed version
- 2026-11-07 (earliest version still in the registry; older removed versions would be earlier)
- Registry data
- snapshot 2026-11-07
- Package and repository
- checked 2026-11-07
Dead or stale signals
None found in the records we hold
Looked for and not found: deprecated in the registry. Does not apply: 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 1.1.0 (published 2026-11-07).
Source: the official MCP Registry list on 2026-11-06 and on 2026-11-07.
What it is
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- com.scriptmasterlabs · 30 servers
- Repository
- gitlab.com/script-master-labs-llc-group/x402-kit
Source: the registry entry and api.github.com · 2026-11-07.
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 rating0 of 1 record check met · 7 do not apply · 1 not checked
- Not ranked by downloads: not an npm or PyPI package
- Not ranked by stars: no public GitHub repository
- Not metRegistry entry is active and says how to run itThe entry lists no package and no remote address, so a client cannot run it.What changes this check: This check reads the registry entry's status and whether it lists a package or a remote address. Marking an entry deprecated is the publisher's own choice. The registry's documentation says a published version's metadata cannot be changed; a new server.json with a unique version string is how an entry is updated. Versioning published MCP servers
- Not checkedSource repository link opensThe link is not on GitHub; we only open GitHub repositories.
- Does not applyRepository is not archivedNo public GitHub repository to read.
- Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
- Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
- Does not applyPackage names its licence with a standard (SPDX) identifierThe entry lists no package.
- Does not applyThe version the registry lists can be installed and is not withdrawnThe entry lists no package.
- Does not applynpm package carries build provenance (attestation)The entry lists no package.
- Does not applyNo known critical or high advisory in the package or its dependenciesThe entry lists no package.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 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 com.scriptmasterlabs/sml-x402-agent-wallet
Answered from the data aboveWho publishes com.scriptmasterlabs/sml-x402-agent-wallet?
The registry ties the namespace com.scriptmasterlabs to the domain scriptmasterlabs.com; only its owner can publish under it. Its linked repository is gitlab.com/script-master-labs-llc-group/x402-kit. These are facts from the registry and GitHub, not a rating.
Has com.scriptmasterlabs/sml-x402-agent-wallet been security tested?
No. The registry entry declares no package and no remote endpoint, so there is nothing to run.
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 #1The registry entry declares no package and no remote endpoint, so there is nothing to run. — the server's own choice
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. “com.scriptmasterlabs/sml-x402-agent-wallet: MCP server record.” Data checked 2026-11-07. https://protocolprobe.com/mcp/servers/com.scriptmasterlabs/sml-x402-agent-wallet
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/com.scriptmasterlabs/sml-x402-agent-wallet)
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