ygo-meta-mcp@1.1.2
CAUTIONPublisher claims: "Multi-source competitive metagame intelligence and tournament discovery Model Context Protocol (MCP) server." Observed in sandbox: sends data to 172.66.151.92, 104.20.45.245, 2606:4700:10::ac42:975c, 2606:4700:10::6814:2df5, 172.67.74.210, 104.26.14.44, 104.26.15.44, 2606:4700:20::681a:f2c, 2606:4700:20::ac43:4ad2, 2606:4700:20::681a:e2c, 192.241.183.183, 2606:4700:20::681a:d8b, 2606:4700:20::681a:c8b, 2606:4700:20::ac43:4a54, 104.26.13.139, 172.67.74.84, 104.26.12.139.
Coverage
Server started and answered tools/list.- Tested
- MCP initialize and tools/list · every tool description, for hidden instructions · every file read, file written and host contacted by what ran
- Not tested
- what the tools do when called with real credentials
Before you give it your token
- It will ask for
- no credential variables read in the code
- Where it talks to
- no vendor host named in the codeAlso ygoprodeck.com, yugiohmeta.com, roadoftheking.com, masterduelmeta.com — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · contacted 172.66.151.92, 104.20.45.245, 2606:4700:10::ac42:975c, 2606:4700:10::6814:2df5, 172.67.74.210, 104.26.14.44, 104.26.15.44, 2606:4700:20::681a:f2c, 2606:4700:20::ac43:4ad2, 2606:4700:20::681a:e2c, 192.241.183.183, 2606:4700:20::681a:d8b, 2606:4700:20::681a:c8b, 2606:4700:20::ac43:4a54, 104.26.13.139, 172.67.74.84, 104.26.12.139 (undeclared)
- What we could not test
- what the tools do when called with real credentials
Find out what these hosts are first. In the honeypot it contacted 172.66.151.92, 104.20.45.245, 2606:4700:10::ac42:975c, 2606:4700:10::6814:2df5, 172.67.74.210, 104.26.14.44, 104.26.15.44, 2606:4700:20::681a:f2c, 2606:4700:20::ac43:4ad2, 2606:4700:20::681a:e2c, 192.241.183.183, 2606:4700:20::681a:d8b, 2606:4700:20::681a:c8b, 2606:4700:20::ac43:4a54, 104.26.13.139, 172.67.74.84, 104.26.12.139, which nothing in the package names as its own. If that is the vendor's service, fine; if you cannot place it, do not connect it.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios) on 2026-11-10 and scored it 70/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Summary: sends data to 172.66.151.92, 104.20.45.245, 2606:4700:10::ac42:975c, 2606:4700:10::6814:2df5, 172.67.74.210, 104.26.14.44, 104.26.15.44, 2606:4700:20::681a:f2c, 2606:4700:20::ac43:4ad2, 2606:4700:20::681a:e2c, 192.241.183.183, 2606:4700:20::681a:d8b, 2606:4700:20::681a:c8b, 2606:4700:20::ac43:4a54, 104.26.13.139, 172.67.74.84, 104.26.12.139.
Behavior trace
Honeypot run · 25 s · 2 scenariosStatic findings
No findings across 1,943 lines in 30 files.
Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for ygo-meta-mcp@1.1.2 as of 4d ago. This is the package itself, not its dependencies.
What would make this Verified
10 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Contacts a host you did not declare≈ +23 on the totalList every host you talk to in SKILL.md frontmatter (`network: [api.example.com]`), or stop contacting the ones you cannot justify.
- Unclaimed publisher≈ +8 on the totalClaim nedsonbr: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.