test-mcp
Skill1 starsChanged 37 days agoMITView on GitHub
Test the MCP server by sending JSON-RPC requests and validating tool responses
1 other project uses a version of this.
Adopted by
Most recently taken up by
- tomaspavlin/rohlik-mcptheir own version, first seen Mar 17, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- tomaspavlin/rohlik-mcp★ 119same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- build-checkSkill
- test-compareSkill
- test-extractSkill
- clone-pageSkill
- extractSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Test the snipkiwi MCP server by simulating JSON-RPC tool calls.
- Very specific: line 22
Verify extract_tailwind tool is listed
- Distinctive: line 24
Check input schemas are valid
- Distinctive: line 31
Verify response contains content
- Distinctive: line 32
Check for Tailwind HTML in output
- Distinctive: line 33
Verify no error responses
- Distinctive: line 42
If no arguments, just test tool listing (fast, no browser needed).
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Test MCP Server
Test the snipkiwi MCP server by simulating JSON-RPC tool calls.
Steps
- Build first:
npx tsc - Test tool listing: Send initialize + tools/list request to the MCP server
echo '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"test","version":"1.0"}}} {"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}' | timeout 10 node dist/mcp-server.js 2>/dev/null- Verify
extract_tailwindtool is listed - Verify
list_page_elementstool is listed - Check input schemas are valid
- Verify
- Test extraction tool (if URL provided):
echo '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"test","version":"1.0"}}} {"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"extract_tailwind","arguments":{"url":"$0","selector":"$1"}}}' | timeout 60 node dist/mcp-server.js 2>/dev/null- Verify response contains content
- Check for Tailwind HTML in output
- Verify no error responses
- Report:
- MCP protocol compliance (initialize handshake)
- Tool discovery (list_page_elements, extract_tailwind)
- Extraction result quality (if URL tested)
Default test
If no arguments, just test tool listing (fast, no browser needed).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

