UseGrant MCP Server

Created By
usegranthqa year ago
MCP server for usegrant
Overview

What is UseGrant MCP Server?

UseGrant MCP Server is a Model Context Protocol (MCP) server designed for interacting with the UseGrant API, providing tools for managing providers, clients, tenants, and access tokens.

How to use UseGrant MCP Server?

To use the MCP Server, you need to have Node.js 16 or higher and a valid UseGrant API key. You can configure it with the Claude desktop by adding specific settings to your configuration file.

Key features of UseGrant MCP Server?

  • List, create, and delete providers and clients.
  • Manage tenants and their associated providers.
  • Generate and validate access tokens for clients.

Use cases of UseGrant MCP Server?

  1. Managing user access and permissions in applications.
  2. Integrating with third-party services that require authentication.
  3. Facilitating secure API interactions through token management.

FAQ from UseGrant MCP Server?

  • What is the Model Context Protocol (MCP)?

MCP is a protocol that allows for standardized interactions with various services and APIs.

  • Do I need an API key to use the MCP Server?

Yes, a valid UseGrant API key is required to authenticate your requests.

  • Is there any specific environment setup required?

You need Node.js 16 or higher and to configure your environment with the necessary API key.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
usegranthq
Star
0
Language
JavaScript
License
MIT license
Tags

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.

21 hours ago