AIND Metadata access MCP server

Created By
AllenNeuralDynamicsa year ago
MCP server for AIND metadata
Overview

what is AIND Metadata access MCP server?

AIND Metadata access MCP server is a server designed to facilitate access to AIND metadata through a structured interface.

how to use AIND Metadata access MCP server?

To use the MCP server, configure your MCP clients with the provided JSON structure to integrate the server into your applications.

key features of AIND Metadata access MCP server?

  • Easy integration with MCP clients using JSON configuration.
  • Supports commands for data access.
  • Compatible with various development environments like Claude Desktop App and VSCode.

use cases of AIND Metadata access MCP server?

  1. Accessing AIND metadata for research purposes.
  2. Integrating metadata access into applications for enhanced data management.
  3. Facilitating data-driven decision-making in projects.

FAQ from AIND Metadata access MCP server?

  • What programming language is used for the server?

The server is developed in Python.

  • Is there a license for the server?

Yes, the server is licensed under the MIT license.

  • How can I configure the server in my application?

You can configure the server by adding the specified JSON structure to your MCP client settings.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
AllenNeuralDynamics
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

11 hours ago
Voyei

an hour ago