Skip to main content
Glama
127,309 tools. Last updated 2026-05-05 13:48

"An MCP that complies with Data Act and ISO 27001 standards" matching MCP tools:

  • Multipart file upload for content that exceeds a single model response's output token cap (big SPA bundles, large seed data, inline vendor libs). Flow: first call with chunk_index=0 and NO upload_id — response returns an upload_id. Subsequent calls pass that upload_id with chunk_index=1, 2, 3…. Last call sets final=true to atomically concatenate and commit as one ProjectFile. Chunks are staged in Redis with a 10-minute TTL. chunk_index overwrites (safe to retry). Max chunk size: 64 KB. Max assembled file: 20 MB.
    Connector
  • List recent execution traces for an agent — the same data as /admin/requests, scoped to one agent and readable by an LLM. Use this when an agent call timed out, drafted the wrong response, or you want to know which tool/LLM call burned the latency. Pair with `agents.trace_get` for full detail on a specific trace. Filters: `status`, `success`, `source` (single value or comma-separated: `agent,voice`), `date_from`/`date_to` (ISO-8601), pagination via `limit`/`offset`. Returns `returned_count`, `dropped_on_page` (should be 0 — positive means the backend agent_id predicate let something through), and `has_more`. Edge case: a raw page of all-dedup-dropped rows yields `returned_count=0, has_more=true`; re-call with `offset += limit`.
    Connector
  • Statistically validated leading indicator signals evaluated against live supply chain data. Each signal is a Granger-causal relationship tested at p<=0.01 with directional accuracy >=55%. Signals predict commodity price movements, manufacturing shifts, and macroeconomic changes 1 week to 6 months ahead. Returns ACTIVE (threshold crossed — act now), WATCH (approaching threshold — prepare), or CLEAR status for each signal. 58 signals across 3 tiers organized by predictor group (GDI pillars, SMI regions, cross-index spreads). Used by commodity traders for forward-looking positioning, procurement teams for buy/defer timing, and hedge funds for alternative data signals.
    Connector
  • START HERE - Returns the complete Stratalize tool catalog: 194 governed MCP tools across 6 namespaces (crypto, finance, governance, healthcare, realestate, intelligence). 124 tools available via x402 (USDC micropayments on Base): 122 paid + 2 free reference tools. 139 additional tools accessible via OAuth-authenticated MCP for organizations. Call this first to discover C-suite briefs (CEO, CFO, CRO, CMO, CTO, CHRO, CX, GC, COO), market benchmarks, governance compliance tools (EU AI Act, FS AI RMF, UK FCA), and org intelligence with role-based recommendations. No auth required.
    Connector
  • Full AI visibility audit across 67+ checks in 12 categories (4 AEO + 4 GEO + 4 Agent Readiness). Returns detailed per-check scores with specific issues and recommendations, AI Identity Card with mention readiness and detected competitors, and business profile. GEO checks include 3 research-backed citation signals: factual density, answer frontloading, and source citations. Agent Readiness covers emerging agent-discovery standards Cloudflare's isitagentready.com evaluates: RFC 9727 api-catalog, SEP-1649 MCP Server Card, and IETF Content-Signal (draft-romm-aipref). Does NOT generate fix code — use fix_site for that, or compare_sites to benchmark against a competitor. Pay per call ($1.00) via x402 — USDC on Base or Solana. Machine payment via signed X-PAYMENT header; see https://www.x402.org/. On payment_required, the response includes the full x402 payload with payTo/amount/asset.
    Connector
  • Submit an extension request for existing delegated resources on TronSave via authenticated REST `POST /v2/extend-request`. Requires a logged-in MCP session created by the `tronsave_login` tool: include `mcp-session-id: <sessionId>` returned by `tronsave_login` on subsequent MCP requests. Internal tools never accept API keys via tool arguments; the server forwards the API key cached in session to TronSave internal REST endpoints. Side effect: creates an extension order and may commit TRX from the internal account. `extendData` must follow the REST contract (see schema on each row). Populate it from TronSave outside this MCP—for example the authenticated `POST /v2/get-extendable-delegates` response field `extendData`, or another TronSave client. Do not copy rows blindly from `tronsave_list_extendable_delegates` (GraphQL); that payload shape differs and is for market discovery only.
    Connector

Matching MCP Servers

  • A
    license
    B
    quality
    F
    maintenance
    A self-learning AI standards system that automatically detects patterns from user corrections and updates AI configuration files. Learns from repeated corrections (like 'use uv not pip') and automatically generates CLAUDE.md and other AI assistant configuration files.
    Last updated
    9
    3
    MIT
  • A
    license
    -
    quality
    C
    maintenance
    Transforms static coding standards into a queryable live data store for AI agents, delivering task-specific rules and fix guidance on demand. This optimizes context window usage through progressive disclosure, ensuring agents apply relevant governance without loading massive documentation.
    Last updated
    2
    MIT

Matching MCP Connectors

  • send-that-email MCP — wraps StupidAPIs (requires X-API-Key)

  • EU AI Act + GDPR compliance scanner. One call, no arguments, 10 seconds. 22 AI frameworks detected.

  • Statistically validated leading indicator signals evaluated against live supply chain data. Each signal is a Granger-causal relationship tested at p<=0.01 with directional accuracy >=55%. Signals predict commodity price movements, manufacturing shifts, and macroeconomic changes 1 week to 6 months ahead. Returns ACTIVE (threshold crossed — act now), WATCH (approaching threshold — prepare), or CLEAR status for each signal. 58 signals across 3 tiers organized by predictor group (GDI pillars, SMI regions, cross-index spreads). Used by commodity traders for forward-looking positioning, procurement teams for buy/defer timing, and hedge funds for alternative data signals.
    Connector
  • Validate structured data and automatically compute repairs if it fails. Single call that combines validate + repair. If PASS: returns the validated data with determinism hash. If FAIL: returns the failure details AND a repaired payload with field-by-field corrections and confidence scores. The agent can inspect the repairs and resubmit the corrected data. If REVIEW: returns the flagged data with review reasoning. This is the recommended starting point for most agent integrations. Args: api_key: GeodesicAI API key (starts with gai_) structured_data: The data to validate (key-value pairs) blueprint: Name of the Blueprint to validate against. Use list_blueprints to see options.
    Connector
  • Look up a single paper by its DOI. Args: doi: The DOI of the paper (e.g. "10.1038/s41586-024-07386-0"). api_key: Optional: Your Stripe subscription ID for paid access. Get one at https://bgpt.pro/mcp Returns: Paper with title, DOI, Raw Data, methods, results, quality scores, and 25+ metadata fields — or an error if not found. Costs $0.02 if found, free if not.
    Connector
  • Lists Vocab Voyage's MCP starter prompts (also exposed via the standard MCP prompts/list endpoint). Useful for hosts that don't yet support prompts/list.
    Connector
  • Computes Jaimini Char Dasha from birth data and returns sign lords as period rulers with ISO-dated Maha and Antar sequences plus karaka mappings. SECTION: WHAT THIS TOOL COVERS Uses the Jaimini system where rashis (not grahas) rule time periods, including Atmakaraka, eight karakas, current Maha/Antar labels in Sanskrit signs, and a period array with nested antardashas. It does not return Vimshottari (asterwise_get_dasha), Yogini, or Ashtottari timelines. SECTION: WORKFLOW BEFORE: RECOMMENDED — asterwise_get_natal_chart — contextualises the chart before interpreting sign-based lords. AFTER: asterwise_get_dasha — optional Vimshottari cross-check for the same native. SECTION: INPUT CONTRACT Period start_date and end_date in data.periods[] are YYYY-MM-DD (ISO), unlike asterwise_get_dasha which uses DD/MM/YYYY in its tree. All other parameters follow the BirthData global contract. SECTION: OUTPUT CONTRACT data.atmakaraka (string — planet name) data.start_rashi (string — Sanskrit rashi name) data.start_rashi_index (int) data.karakas{} — object mapping Jaimini karaka keys to planet names data.current_mahadasha (string — Sanskrit rashi name, e.g. 'Mithuna') data.current_antardasha (string — Sanskrit rashi name) data.periods[] — Mahadasha objects: rashi (string) rashi_index (int) years (int) start_date (string — YYYY-MM-DD ISO) end_date (string — YYYY-MM-DD ISO) antardashas[] — same shape as one level (no further nesting) SECTION: RESPONSE FORMAT response_format=json serialises the complete response as indented JSON — use this for programmatic parsing, typed clients, and downstream tool chaining. response_format=markdown renders the same data as a human-readable report. Both modes return identical underlying data — no fields are added, removed, or filtered by either mode. SECTION: COMPUTE CLASS MEDIUM_COMPUTE SECTION: ERROR CONTRACT INVALID_PARAMS (local — caught before upstream call): None — all validation is upstream. INVALID_PARAMS (upstream): — None — upstream rejection surfaces as MCP INTERNAL_ERROR at the tool layer. INTERNAL_ERROR: — Any upstream API failure or timeout → MCP INTERNAL_ERROR Edge cases: — Two planets at the same degree: classical tie-break rules apply upstream; no separate error. SECTION: DO NOT CONFUSE WITH asterwise_get_dasha — Vimshottari planet lords with DD/MM/YYYY in periods[], not sign-based Jaimini Char Dasha. asterwise_get_yogini_dasha — eight Yoginis and data.periods.root[], not Jaimini signs.
    Connector
  • Unlocks access to other MCP tools. All tools remain locked with a "Session Not Initialized" error until this function is successfully called. Skipping this explicit initialization step will cause all subsequent tool calls to fail. MANDATORY FOR AI AGENTS: The returned instructions contain ESSENTIAL rules that MUST govern ALL blockchain data interactions. Failure to integrate these rules will result in incorrect data retrieval, tool failures and invalid responses. Always apply these guidelines when planning queries, processing responses or recommending blockchain actions. COMPREHENSIVE DATA SOURCES: Provides an extensive catalog of specialized blockchain endpoints to unlock sophisticated, multi-dimensional blockchain investigations across all supported networks.
    Connector
  • Lists sign ingresses and retrograde/direct stations for all planets between two dates against the natal context and returns chronological astronomical events. SECTION: WHAT THIS TOOL COVERS Aggregates ingress rows (with sankranti flag for Sun) and station rows with Julian day, local ISO timestamps, and ecliptic longitude. The upstream API enforces ordering and a 24-month window; violations are not pre-checked in this MCP layer. It does not return today's full Gochar row (asterwise_get_gochar) or dasha-transit scores (asterwise_get_dasha_transits). SECTION: WORKFLOW BEFORE: RECOMMENDED — asterwise_get_natal_chart — clarifies the natal reference for the same birth data. AFTER: asterwise_get_gochar — optional current snapshot after scanning the range. SECTION: INPUT CONTRACT from_date and to_date are strings in the format expected by the upstream API (typically YYYY-MM-DD). Range cap (24 months), date order, and validity are enforced upstream, not locally. SECTION: OUTPUT CONTRACT data.ingresses[] — each: planet (string) from_sign (int — 0–11) to_sign (int — 0–11) jd (float) date_iso (string — ISO datetime, local time) is_sankranti (bool — true for Sun ingresses only) retrograde_ingress (bool) data.stations[] — each: planet (string) station_type (string — 'retrograde' or 'direct') jd (float) date_iso (string — ISO datetime) longitude (float) SECTION: RESPONSE FORMAT response_format=json serialises the complete response as indented JSON — use this for programmatic parsing, typed clients, and downstream tool chaining. response_format=markdown renders the same data as a human-readable report. Both modes return identical underlying data — no fields are added, removed, or filtered by either mode. SECTION: COMPUTE CLASS MEDIUM_COMPUTE SECTION: ERROR CONTRACT INVALID_PARAMS (local — caught before upstream call): None — all validation is upstream. INVALID_PARAMS (upstream): — None — range/order violations surface as MCP INTERNAL_ERROR at the tool layer. INTERNAL_ERROR: — Any upstream API failure or timeout → MCP INTERNAL_ERROR Edge cases: — Exceeding the 24-month cap or bad date order fails upstream and is not turned into MCP INVALID_PARAMS here. SECTION: DO NOT CONFUSE WITH asterwise_get_gochar — single-day transit snapshot with houses from Moon/Lagna, not ingress/station lists. asterwise_get_dasha_transits — dasha lord vs transit scoring for today only.
    Connector
  • Returns one row per civil day for a calendar month at a location with condensed tithi, vara, nakshatra, yoga, karana, and rahu_kaal columns. SECTION: WHAT THIS TOOL COVERS Month-wide Panchanga suitable for planners; each day includes ending times where applicable and local Rahu Kaal bounds. Year must be 1900–2100 and month 1–12 (Pydantic on PanchangaCalendarInput). It is not single-day detailed Panchanga (asterwise_get_panchanga) nor muhurta search (asterwise_get_muhurta). SECTION: WORKFLOW BEFORE: None — this tool is standalone. AFTER: asterwise_get_panchanga — expand any single day at full detail. SECTION: INPUT CONTRACT year/month/lat/lon validated locally. Timezone handling follows upstream response fields (data.timezone echo). SECTION: OUTPUT CONTRACT data.year (int) data.month (int) data.timezone (string) data.ayanamsa (string) data.days[] — 28–31 objects: date (string — YYYY-MM-DD) tithi — { name (string), number (int), paksha (string), end_time (string — ISO UTC) } vara — { name (string), number (int), lord (string) } nakshatra — { name (string), index (int), pada (int), end_time (string — ISO UTC) } yoga — { name (string), index (int), is_inauspicious (bool), end_time (string — ISO UTC) } karana — { name (string), number (int), end_time (string — ISO UTC) } rahu_kaal — { start (string — HH:MM local), end (string — HH:MM local) } SECTION: RESPONSE FORMAT response_format=json serialises the complete response as indented JSON — use this for programmatic parsing, typed clients, and downstream tool chaining. response_format=markdown renders the same data as a human-readable report. Both modes return identical underlying data — no fields are added, removed, or filtered by either mode. SECTION: COMPUTE CLASS FAST_LOOKUP SECTION: ERROR CONTRACT INVALID_PARAMS (local — caught before upstream call): — year outside 1900–2100 → MCP INVALID_PARAMS — month outside 1–12 → MCP INVALID_PARAMS — lat/lon out of range → MCP INVALID_PARAMS INVALID_PARAMS (upstream): — None — further rejection surfaces as MCP INTERNAL_ERROR at the tool layer. INTERNAL_ERROR: — Any upstream API failure or timeout → MCP INTERNAL_ERROR Edge cases: — Day count follows the civil month (28–31 entries). SECTION: DO NOT CONFUSE WITH asterwise_get_panchanga — deep single-day Panchanga with degree fields, not a month grid. asterwise_get_muhurta — activity-ranked windows, not a passive calendar.
    Connector
  • Build an AccountPermissionUpdate transaction that grants the PowerSun platform permission to delegate/undelegate resources and optionally vote on your behalf. Returns an unsigned transaction that you must sign with your private key and then broadcast using broadcast_signed_permission_tx. All existing account permissions are preserved. Requires authentication.
    Connector
  • Create an authenticated server session and return a `sessionId` for subsequent tool calls. Default mode is wallet signature login for platform tools; secondary mode is `apiKey` login for internal tools. For wallet login, ALWAYS call `tronsave_get_sign_message` first, sign that exact message client-side, then call `tronsave_login` with `signature_timestamp` in exact format `<signature>_<timestamp>` (signature and timestamp joined by `_`). Use returned `sessionId` as `mcp-session-id` on every subsequent request.
    Connector
  • Enforce a guardrail: verify an agent action against a compiled policy using formal verification. An SMT solver — not an LLM — determines whether the action satisfies every rule. Returns SAT (allowed) or UNSAT (blocked) with extracted values and a cryptographic ZK proof that the check was performed correctly. Cannot be jailbroken. 1 credit ($0.01). Requires api_key. Tip: end the action with an explicit claim like 'I assert this complies with the policy' for best extraction.
    Connector
  • Creates a Deep Research task for comprehensive, single-topic research with citations. USE THIS for analyst-grade reports, NOT for batch data enrichment. Use Parallel Search MCP for quick lookups. After calling, share the URL with the user and STOP. Do not poll or check results unless otherwise instructed. Multi-turn research: The response includes an interaction_id. To ask follow-up questions that build on prior research, pass that interaction_id as previous_interaction_id in a new call. The follow-up run inherits accumulated context, so queries like "How does this compare to X?" work without restating the original topic. Note: the first run must be completed before the follow-up can use its context.
    Connector
  • AI-powered company analysis using semantic search over Nordic financial data. Orchestrates multiple searches internally and returns a synthesized narrative answer with source citations. Covers annual reports, quarterly reports, press releases and macroeconomic context for Nordic listed companies. Use this when you want a synthesized answer rather than raw search chunks. For raw data access, use search_filings or company_research instead. For a full due diligence report with AI-planned sections, use the Alfred MCP server: alfred.aidatanorge.no/mcp Args: company: Company name or ticker question: What you want to know about the company model: 'haiku' (default) or 'sonnet'
    Connector
  • START HERE - Returns the complete Stratalize tool catalog: 194 governed MCP tools across 6 namespaces (crypto, finance, governance, healthcare, realestate, intelligence). 124 tools available via x402 (USDC micropayments on Base): 122 paid + 2 free reference tools. 139 additional tools accessible via OAuth-authenticated MCP for organizations. Call this first to discover C-suite briefs (CEO, CFO, CRO, CMO, CTO, CHRO, CX, GC, COO), market benchmarks, governance compliance tools (EU AI Act, FS AI RMF, UK FCA), and org intelligence with role-based recommendations. No auth required.
    Connector