ClawHub

Bytesagain Mcp

v1.0.1

Connect AI agents to BytesAgain skill search via MCP SSE. Shows setup commands for OpenClaw, Claude Desktop, and curl. No files modified.

⭐ 0· 18·0 current·0 all-time
by@bytesagain-lab
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
Requires sensitive credentials
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name/description claim to connect agents to BytesAgain MCP SSE. The included script only contacts https://bytesagain.com, prints setup snippets for OpenClaw/Claude/curl, and lists tools — no unrelated credentials, binaries, or config paths are requested.
ℹ
Instruction Scope
SKILL.md and the script instruct the user to modify their client config (example path for Claude is shown) but do not modify files automatically. The script issues HTTP POSTs (initialize, tools/list) to the BytesAgain endpoint and prints/parses responses locally. Be aware that connecting an agent to a remote MCP server gives that server the ability to advertise tools and receive whatever RPC payloads the agent sends; inspect responses before trusting them.
✓
Install Mechanism
No install spec — instruction-only with a small helper script. No downloads or archive extraction; script only requires curl, python3, and mktemp which are reasonable for its functionality.
✓
Credentials
No environment variables, credentials, or uncommon config paths are requested. The network access is limited to the documented bytesagain.com endpoint; this matches the stated purpose.
✓
Persistence & Privilege
always is false and the skill does not request persistent or system-wide modifications. It does recommend restarting the gateway/client after adding the server, which is normal for MCP integrations.
Assessment
This skill is small and appears to do only what it says: show setup commands and test a public MCP endpoint. Before you use it: (1) verify you trust https://bytesagain.com (check the site and TLS certificate); (2) back up any client config file before pasting the suggested JSON into it; (3) run scripts/script.sh test to see what the endpoint returns and inspect the JSON response; (4) remember that connecting your agent to a remote MCP server lets that server offer tools that your agent may call — only connect to services you trust. If you are uncomfortable with autonomous model invocation of remote tools, consider restricting the skill or disabling autonomous invocation in your agent settings.

Like a lobster shell, security has layers — review code before you run it.

latestvk97b3ppht8bpnbyehvgahrkgm5853fh4

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments