Permite que los agentes de IA accedan a datos de la blockchain de Stacks, gestionen subgraphs y configuren webhooks a través de una API alojada o una instancia local.
También conocido como ryanwaits/secondlayer, @secondlayer/mcp
- Stars
- 8
- Herramientas
- 2
- Descargas, 30 días
- —
- Última versión
- 11.6.6
- Último commit
- 13 nov 2026
- Licencia
- MIT
¿Qué es secondlayer MCP?
secondlayer es un MCP server. Permite que los agentes de IA accedan a datos de la blockchain de Stacks, gestionen subgraphs y configuren webhooks a través de una API alojada o una instancia local. Expone 2 herramientas, como fields, count.
Resumen generado a partir del README del proyecto
Acerca del MCP server de secondlayer
Los desarrolladores que construyen sobre la blockchain de Stacks pueden usar este servidor para proporcionar a los agentes de IA acceso directo a los datos de la blockchain y a la gestión de infraestructura. Permite que los agentes realicen lecturas de índices, gestionen el ciclo de vida completo de los subgraphs y configuren webhooks para reaccionar a eventos brutos de la cadena. El servidor es compatible tanto con una API alojada mediante inicio de sesión en el navegador como con instancias locales gestionadas a través de una interfaz de línea de comandos.
Los usuarios pueden conectarse vía stdio para la integración con IDEs o usar un transporte HTTP para configuraciones remotas. Aunque muchas herramientas de indexación y descubrimiento de contratos son públicas, la gestión de subgraphs o webhooks requiere un INSTANCE_TOKEN para configuraciones locales o una SECONDLAYER_API_KEY para el servicio alojado. El conjunto de herramientas se centra en operaciones de alto valor como el despliegue de subgraphs, la reindexación y las pruebas de webhooks, mientras que las consultas de datos más granulares se reservan para la API REST.
Qué puedes hacer con él
- 1Gestionar ciclos de vida de subgraphsUn agente de IA puede desplegar, reindexar o eliminar subgraphs personalizados para organizar los datos de la blockchain.
- 2Automatizar configuraciones de webhooksLos desarrolladores pueden instruir a un agente para crear y probar webhooks que se activen ante llamadas a contratos o eventos específicos.
- 3Consultar datos decodificados de la blockchainUn agente puede recuperar información específica de filas decodificadas utilizando herramientas de indexación para transacciones o transferencias.
- 4Verificar archivos de la blockchainEl servidor permite que los agentes inicien y verifiquen archivos para asegurar la integridad de los datos.
Escrito a partir del README del proyecto. Cada caso de uso se verifica con una cita del mismo.
Cómo instalar secondlayer MCP
Formatos verificados el 10 nov 2026Añadir a CursorAñadir a GooseInstalar secondlayer MCP en Claude Code
$ claude mcp add --env 'SECONDLAYER_API_KEY=<YOUR_SECONDLAYER_API_KEY>' secondlayer -- npx -y @secondlayer/mcpInstalar secondlayer MCP en Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"secondlayer": {
"command": "npx",
"args": [
"-y",
"@secondlayer/mcp"
],
"env": {
"SECONDLAYER_API_KEY": "<YOUR_SECONDLAYER_API_KEY>"
}
}
}
}Instalar secondlayer MCP en VS Code
.vscode/mcp.json
{
"servers": {
"secondlayer": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@secondlayer/mcp"
],
"env": {
"SECONDLAYER_API_KEY": "<YOUR_SECONDLAYER_API_KEY>"
}
}
}
}Instalar secondlayer MCP en VS Code CLI
$ code --add-mcp '{"name":"secondlayer","type":"stdio","command":"npx","args":["-y","@secondlayer/mcp"],"env":{"SECONDLAYER_API_KEY":"<YOUR_SECONDLAYER_API_KEY>"}}'Instalar secondlayer MCP en Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"secondlayer": {
"command": "npx",
"args": [
"-y",
"@secondlayer/mcp"
],
"env": {
"SECONDLAYER_API_KEY": "<YOUR_SECONDLAYER_API_KEY>"
}
}
}
}Instalar secondlayer MCP en Codex
$ codex mcp add secondlayer --env 'SECONDLAYER_API_KEY=<YOUR_SECONDLAYER_API_KEY>' -- npx -y @secondlayer/mcpInstalar secondlayer MCP en Codex config.toml
~/.codex/config.toml
[mcp_servers.secondlayer] command = "npx" args = ["-y", "@secondlayer/mcp"] [mcp_servers.secondlayer.env] SECONDLAYER_API_KEY = "<YOUR_SECONDLAYER_API_KEY>"
Instalar secondlayer MCP en Gemini CLI
$ gemini mcp add -s user -e 'SECONDLAYER_API_KEY=<YOUR_SECONDLAYER_API_KEY>' secondlayer npx -- -y @secondlayer/mcpInstalar secondlayer MCP en Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"secondlayer": {
"command": "npx",
"args": [
"-y",
"@secondlayer/mcp"
],
"env": {
"SECONDLAYER_API_KEY": "<YOUR_SECONDLAYER_API_KEY>"
}
}
}
}Herramientas de secondlayer MCP 2
Detectado desde el READMEfieldscount
| fields | — | |
| count | — |
Configuración
SECONDLAYER_API_KEYSecretoAccount API key (sk-sl_*) for the hosted API: credits, writes.
INSTANCE_TOKENSECONDLAYER_API_URLInstance API URL. Use https://api.secondlayer.tools for hosted.
SECONDLAYER_MCP_SECRET
| Nombre | Descripción | Tipo |
|---|---|---|
| SECONDLAYER_API_KEY | Account API key (sk-sl_*) for the hosted API: credits, writes. | Secreto |
| INSTANCE_TOKEN | — | |
| SECONDLAYER_API_URL | Instance API URL. Use https://api.secondlayer.tools for hosted. | |
| SECONDLAYER_MCP_SECRET | — |
Verificaciones automáticas
Ejecutado 12 nov 2026Informe completo →Pasó nuestras verificaciones automáticas. Esto no es una auditoría de seguridad: lee el código y dale al servidor el acceso más limitado que necesite. Cómo funcionan las verificaciones
- Repositorio de origen vinculado y accesibleAprobado
- Licencia de código abierto (OSI)Aprobado
- Commit o lanzamiento en el último añoAprobado
- El nombre del paquete no es similar a un paquete popularAprobado
- El endpoint remoto usa HTTPSAprobado
- Las herramientas destructivas están etiquetadasAprobado
- Sin instrucciones ocultas para el modeloAprobado
- No hay avisos críticos en el paquete ni en sus dependenciasAprobado
README
Ver en GitHub@secondlayer/mcp
Gives your coding agent direct access to Stacks data, on the hosted API
(api.secondlayer.tools) or on your own instance:
Index (decoded rows), Subgraphs (tables you define, served from your account or instance),
and Streams (raw inputs). Exposes the golden-path tools only: Index reads, the
subgraph lifecycle, webhooks, contract discovery/scaffolding, instance
status, archive verify/bootstrap, and hosted credits/quote. Everything else
(single-record lookups, mempool, PoX, proofs, live Streams reads) is
available over REST /v1 + OpenAPI. There is no consume tool.
Hosted
No install: the hosted API serves the read tools over Streamable HTTP, with a browser sign-in.
claude mcp add --transport http secondlayer https://api.secondlayer.tools/mcp
Clients without OAuth send Authorization: Bearer <sk-sl_ key>. Subgraph
deploys, webhooks, archive, codegen and instance tools are local only. See
/docs/mcp.
Install
bun add @secondlayer/mcp
Auth
Most reads are public: index_* and contracts_find work with no key. Subgraph tools need an INSTANCE_TOKEN past loopback, and so does GET /v1/subgraphs/<name>/<table> over HTTP ({ rows, next_cursor, tip } cursor envelope); on loopback it is open. There is no per-subgraph public or private flag. streams_dumps needs no key: the dumps manifest is public; the tool only needs SL_STREAMS_DUMPS_URL configured. streams_tip is key-mandatory (keyless → 401). Live Streams list reads are REST-only (GET /v1/streams/*). Writes (deploy, reindex, delete, webhooks) need a key, and the key follows the host: on https://api.secondlayer.tools the server uses SECONDLAYER_API_KEY (sk-sl_*) automatically; anywhere else it uses INSTANCE_TOKEN from secondlayer init. Hosted credits/quote use SECONDLAYER_API_KEY too. On the hosted API, subgraph sources are limited to event filters and contract_call/contract_deploy (422 SOURCE_NOT_HOSTABLE otherwise); set startBlock. Read secondlayer://context first: it reports auth state and read-auth tiers.
Quick Start — Stdio (IDE)
Add to your Claude Desktop or Cursor config:
{
"mcpServers": {
"secondlayer": {
"command": "bunx",
"args": ["-p", "@secondlayer/mcp", "secondlayer-mcp"],
"env": {
"SECONDLAYER_API_URL": "http://127.0.0.1:3800",
"INSTANCE_TOKEN": "..."
}
}
}
}
Quick Start — HTTP (Remote)
export SECONDLAYER_API_URL=http://127.0.0.1:3800
export INSTANCE_TOKEN=<from secondlayer init>
export SECONDLAYER_MCP_SECRET=your-secret
bunx -p @secondlayer/mcp secondlayer-mcp-http
# Listening on port 3100
Environment Variables
| Variable | Required | Default | Description |
|---|---|---|---|
INSTANCE_TOKEN |
Writes on your instance | — | From secondlayer init. Required for write tools elsewhere than api.secondlayer.tools; reads are public. Not sent to the hosted API. |
SECONDLAYER_API_KEY |
Hosted API, credits/quote/latest | — | sk-sl_*, used automatically when SECONDLAYER_API_URL is https://api.secondlayer.tools. |
SECONDLAYER_API_URL |
No | http://127.0.0.1:3800 |
Instance API, or https://api.secondlayer.tools for hosted. |
SECONDLAYER_BIN |
CLI tools | secondlayer on PATH |
Path to the CLI binary (bootstrap, repair). |
SECONDLAYER_CWD |
CLI tools | process cwd | Compose project directory. |
SECONDLAYER_MCP_PORT |
No | 3100 |
HTTP transport port. |
SECONDLAYER_MCP_SECRET |
No | — | Bearer token for HTTP auth. Disabled if unset. |
Tools
| Domain | Tools |
|---|---|
| Index (9) | index_events, index_ft_transfers, index_nft_transfers, index_contract_calls, index_blocks, index_transactions, index_print_schema, index_discover, batch_query |
| Subgraphs (12) | subgraphs_list, subgraphs_status, subgraphs_spec, subgraphs_scaffold, subgraphs_deploy, subgraphs_delete, subgraphs_query, subgraphs_backfill, subgraphs_reindex, subgraphs_stop, subgraphs_operations, subgraphs_gaps |
| Webhooks (13) | webhooks_create, webhooks_list, webhooks_get, webhooks_update, webhooks_delete, webhooks_test, webhooks_pause, webhooks_resume, webhooks_rotate_secret, webhooks_deliveries, webhooks_dead, webhooks_requeue, webhooks_replay |
| Streams (2) | streams_tip, streams_dumps |
| Contracts (2) | contracts_find, contracts_get_abi |
| Instance (1) | instance_status |
| Archive (5) | archive_verify, archive_bootstrap, archive_repair, archive_latest, archive_quote |
| Credits (1) | credits_balance (needs SECONDLAYER_API_KEY) |
| Account (4) | account_whoami, account_create_key, account_list_keys, account_rotate_key (only when pointed at https://api.secondlayer.tools) |
Verify after mutating: subgraphs_operations for deploy/reindex/backfill/stop,
webhooks_deliveries for create/test/replay. Empty index:
archive_bootstrap, poll instance_status until decoders are ok, then
archive_verify, then codegen_index_schema.
Periphery surfaces (single block/tx lookups, mempool, PoX, proofs,
credits/caps, live Streams reads/SSE) are REST-only: see the OpenAPI spec at
the API host. Live Streams list reads use GET /v1/streams/events.
Point the server at your instance with SECONDLAYER_API_URL (default
http://127.0.0.1:3800). Writes use INSTANCE_TOKEN from
secondlayer init. account_* tools appear only when the server is pointed at
https://api.secondlayer.tools.
webhooks_create triggers
Webhooks fire on raw chain events. Pass a triggers array (contract / event /
function / trait), e.g. [{ "type": "contract_call", "contractId": "SP....amm", "functionName": "swap-*" }]. To react to subgraph rows, read the
table from your own Postgres or poll the subgraph API.
subgraphs_query enhancements
fields— comma-separated column projection (e.g."sender,amount_x")count— boolean, returns row count instead of rows- Filter operators:
eq,neq,gt,gte,lt,lte,like - Max limit: 200
Resources
| URI | Description |
|---|---|
secondlayer://context |
Live state — what exists (your subgraphs, webhooks, account), what you can do, and read-auth tiers. Read first. |
secondlayer://filters |
Subgraph source filter types and their fields |
secondlayer://column-types |
Column type mappings and options |
secondlayer://traits |
SIP trait standards (valid trait values) |
secondlayer://chain-triggers |
Chain-webhook trigger types and fields |
Error Handling
All tools return structured errors with isError: true:
{ "error": { "type": "not_found", "status": 404, "message": "Subgraph not found" } }
| Error type | Status | When |
|---|---|---|
unauthorized |
401 | Invalid or missing API key |
not_found |
404 | Resource doesn't exist |
rate_limited |
429 | Too many requests |
server_error |
5xx | Server-side failure |
error |
other | Validation, bundling, etc. |
Bundle/deploy errors use descriptive prefixes: "Bundle failed:", "Module evaluation failed:", "Validation failed:". HTTP transport enforces a 1MB body limit (413) and JSON parse safety (400). Scaffold ABI fetch has a 10s timeout.
Programmatic Usage
import { createServer } from "@secondlayer/mcp";
const server = createServer();
// Connect to your own transport
License
MIT
Preguntas sobre secondlayer MCP
¿Cómo agrego secondlayer MCP a Claude Code?
Ejecuta claude mcp add --env 'SECONDLAYER_API_KEY=<YOUR_SECONDLAYER_API_KEY>' secondlayer -- npx -y @secondlayer/mcp en tu terminal. Añade --scope user para que esté disponible en todos los proyectos.
¿Cómo agrego secondlayer MCP a Cursor?
Abre ~/.cursor/mcp.json y añade el servidor en mcpServers, usando la configuración de Cursor que se muestra en la sección de instalación de arriba.
¿Qué herramientas proporciona secondlayer MCP?
Expone 2 herramientas, incluidas fields, count.
¿Necesito una API key para todas las herramientas?
No, la mayoría de las lecturas como index_events y contracts_find son públicas y funcionan sin una clave, pero las herramientas de subgraphs y las operaciones de escritura requieren un INSTANCE_TOKEN o una API key.
¿Puedo usar esto con mi propia instancia local?
Sí, puedes apuntar el servidor a tu propia instancia configurando la variable de entorno SECONDLAYER_API_URL.
¿Cuál es el propósito del recurso secondlayer://context?
Se utiliza para informar el estado de autenticación actual y los niveles de lectura-autenticación disponibles.