Skip to main content
Glama
114,467 tools. Last updated 2026-04-21 13:35
  • Get practical cooking tips and expert techniques for any topic. Covers ingredients, methods, equipment, and cuisines. TRIGGERS: - 'how do I X', 'tips for X', 'cooking advice for X' - 'best way to cook X', 'technique for X' - 'help me with X', 'kitchen tips', 'cooking hack for X' TOPICS: knife skills, rice, broth, pho, grilling, baking, fermentation, wok cooking, seasoning, mise en place, sous vide, smoking, braising, and more.
    Connector
  • Get a human's FULL profile including contact info (email, Telegram, Signal), crypto wallets, fiat payment methods (PayPal, Venmo, etc.), and social links. Requires agent_key from register_agent. Rate limited: PRO = 50/day. Alternative: $0.05 via x402. Use this before create_job_offer to see how to pay the human. The human_id comes from search_humans results.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Share context and questions between Claude instances — VS Code, claude.ai web, and mobile.

  • Collect Apple Health data from your wearables through the Context app and query it via MCP

  • Is macro with you or against you? Get the current regime (bull/bear/risk_on/risk_off/choppy), directional signal and confidence, and macro context (DXY, VIX, fear/greed) before entering a position. Data-only, no LLM latency. 17 tokens supported. REST equivalent: POST /analyze/market (0.25 USDC). Args: token: Token symbol (BTC, ETH, SOL, XRP, ADA, DOGE, AVAX, LINK, BNB, ATOM, DOT, ARB, SUI, OP, LTC, AMP, ZEC) context: Optional historical context window ('7d' or '30d'). Adds percentile rankings.
    Connector
  • Search Hansard for parliamentary debates, questions, and speeches. Returns contributions from MPs and Lords including date, party, debate title, and text (capped at 3000 chars per contribution). Useful for understanding legislative intent or political context.
    Connector
  • Task-scoped context briefing. Returns a prioritised context payload shaped by your task description, ranked by risk-if-missed. Constraints and alerts rank above general knowledge. Use at the START of reasoning about a question to get the system's best assessment of what's relevant. Complements query_memory: this gives breadth, query_memory gives depth.
    Connector
  • Check whether a set of constraints can be simultaneously satisfied. Uses the twist-compression operator to detect structural obstructions — fundamental conflicts in the constraint system that cannot be resolved by adjusting any single field. Returns obstruction type, magnitude, and the specific constraint interactions causing the conflict. Fast pre-check before running full validation. Args: api_key: GeodesicAI API key (starts with gai_) constraints: List of derivation rules and formal constraints to check field_values: Current field values (numeric key-value pairs)
    Connector
  • Get authoritative Senzing SDK reference data for flags, migration, and API details. Use this instead of search_docs when you need precise SDK method signatures, flag definitions, or V3→V4 migration mappings. Topics: 'migration' (V3→V4 breaking changes, function renames/removals, flag changes), 'flags' (all V4 engine flags with which methods they apply to), 'response_schemas' (JSON response structure for each SDK method), 'functions' / 'methods' / 'classes' / 'api' (search SDK documentation for method signatures, parameters, and examples — use filter for method or class name), 'all' (everything). Use 'filter' to narrow by method name, module name, or flag name
    Connector
  • Lists all API paths and their HTTP methods with summaries, organized by path. Results can be passed directly into 'get-endpoint'.
    Connector
  • Use this tool to estimate the token count of a text before sending it to an LLM. Triggers: 'how many tokens is this?', 'will this fit in context?', 'check if this is within the limit', 'token count for GPT-4'. Returns estimated token count, percentage of the model's context window used, and estimated API cost. Essential for context window management and cost planning.
    Connector
  • Save development context (reasoning, decisions, trade-offs) for the current coding session. Use after completing a meaningful unit of work. PREFERRED FORMAT: Wrap content in <context> XML tags: <context> <title>Short title of what was done</title> <agent>your-agent-name (model)</agent> <tags>keyword1, keyword2, keyword3</tags> <story> Organize by phases. Write in first-person engineering journal style. Phase 1 — Title: What user asked, what you did, challenges faced, how you resolved them. Include back-and-forth with the user where it shaped the outcome. </story> <reasoning> Why you chose this approach. <decisions> - Decision — rationale </decisions> <rejected> - Alternative — why rejected </rejected> <tradeoffs> - Trade-off accepted — justification </tradeoffs> </reasoning> <files> path/to/file — new — Description path/to/other — modified — Description </files> <tools>MCPs and resources used</tools> <verification>Test/build results</verification> <risks>Open questions or risks</risks> </context> Required tags: title, story, reasoning. All others (including files) are optional. Context ID, repository, branch, date, and commits are auto-populated. CLI alternative: write content to a file, then run `git why save --file context.md`. Or pipe directly: `echo '<context>...</context>' | git why save`.
    Connector
  • Verify domain ownership for a registered agent. The agent must have a websiteUrl set. Supports two methods: "well-known" (place a file at /.well-known/humanpages-verify.txt) or "dns" (add a TXT record at _humanpages.yourdomain.com).
    Connector
  • Get a Stripe billing portal URL for managing payment methods and invoices. Returns a URL (not a redirect) that the human can open in a browser. Requires: API key with read scope. Args: flow: Optional. Set to "payment_method_update" to go directly to the payment method update page. Returns: {"url": "https://billing.stripe.com/p/session/..."}
    Connector
  • Get complete details for one or more businesses including address, phone, website, opening hours, services, payment methods, social links, logo, business image, and coordinates. Pass comma-separated IDs for batch requests.
    Connector
  • Use this tool to estimate the token count of a text before sending it to an LLM. Triggers: 'how many tokens is this?', 'will this fit in context?', 'check if this is within the limit', 'token count for GPT-4'. Returns estimated token count, percentage of the model's context window used, and estimated API cost. Essential for context window management and cost planning.
    Connector
  • Create a new hiring context (company profile) for organizing candidates and JDs. Returns a context object with 'id'. Use this id as context_id in atlas_upload_candidate, atlas_create_jd, atlas_list_candidates, and all analysis/batch/utility tools. This is the first step in the Atlas workflow. Free.
    Connector
  • Get the current visitor auth configuration for a project. Shows whether auth is enabled, which methods are allowed, and the success redirect URL.
    Connector
  • Full-text search across motion-capture, threat-intel, and rehab datasets. Matches labels, paths, competitor names, techniques. Returns full lesson detail with pricing so you can immediately call purchase tools. Free.
    Connector
  • Assemble agent context within budget constraints. Call this at session start to get identity, personality, constitution, facts, goals, lessons, and skills content sized to fit the context window. Each component is truncated to its budget allocation.
    Connector
  • Return the NGSI-LD @context URL and context content for a specific data model. This is required when building valid NGSI-LD linked-data payloads — without the correct @context, the payload is not valid linked data and will be rejected by NGSI-LD brokers. Use this before constructing or validating a normalized payload. Example: get_model_context({"model_name": "WeatherObserved"})
    Connector
  • Returns the full machine-readable service catalog including available services, pricing, and payment methods. Use this to understand what Archangel Agency offers to AI agents.
    Connector
  • Premium stateless decision bundle for one-shot trade gating. Caller provides full context (training/test + optional what-if blocks) and receives verdict, risk score, instability/mechanism signals, and recommendation.
    Connector
  • START HERE. Global market snapshot: top edges (mispriced contracts), price movers, highlights, traditional markets — live exchange data updated every 15 min. With thesisId + apiKey: thesis-specific context including causal tree, edges with orderbook depth, evaluation history, and track record. No auth needed for global context.
    Connector
  • Get comprehensive stock summary: price, ATM IV, historical vol, VRP, skew, term structure, options flow, exposure data, and macro context (VIX, Fear & Greed, yield curve).
    Connector
  • Get volatility risk premium (VRP) dashboard: live IV vs realized vol, VRP percentiles, term structure, regime classification, strategy scores, and macro context.
    Connector
  • List registered external services available to the calling agent. Returns service IDs, display names, allowed methods/paths, and rate limit state. Does not return credentials or credential references.
    Connector
  • Get volatility risk premium (VRP) dashboard: live IV vs realized vol, VRP percentiles, term structure, regime classification, strategy scores, and macro context.
    Connector
  • SUPPLEMENTARY tool — search short notable quotes from executive media appearances. Each quote includes who said it, when, where, and source context. Only use this when the user specifically asks for brief quotations or exact wording. For general research about what an executive has said or thinks, use get_transcripts instead — it provides much richer context.
    Connector
  • Embed invisible DCT-domain watermark into an image. Encodes a text payload into luminance channel frequency coefficients. Survives light compression. FREE. (FREE)
    Connector
  • Deep anomaly analysis with geometric proof. No Blueprint required. Explains WHY data is anomalous using three independent methods: 1. Structural fingerprinting — distance from the learned manifold 2. Cluster analysis — deviation from structural type centroids 3. Twist-compression obstruction — fundamental constraint conflicts Returns a human-readable geometric proof of anomaly, not just a flag. Args: structured_data: The data to analyze for anomalies
    Connector
  • Get enriched news with full AI-generated context and analysis (paid via x402). This premium endpoint returns the complete news data including: - long_context: Detailed AI-generated context about the news event - short_context: Brief contextual summary - Full entity analysis and token mentions Payment is handled via the x402 protocol using USDC on Base network. This tool returns the payment endpoint and instructions.
    Connector
  • Update a hiring context's details (name, industry, size, hiring context). Requires context_id from atlas_create_context or atlas_list_contexts. Returns the updated context object. Free.
    Connector
  • Retrieve a saved context by its ID. Returns the full markdown content including metadata, reasoning, and file changes. Use when you know the exact context ID (e.g., from gitwhy_search or gitwhy_list results) and need the complete details. CLI alternative: `git why get <id>`.
    Connector
  • Returns Hemrock's financial modeling best practices and design principles for a given topic. Useful as background context for AI interactions.
    Connector
  • Create a new message in Teamwork.com. In the context of Teamwork.com, a message is a structured communication post within a project that allows team members to share updates, discuss topics, and document decisions in a centralized, threaded format. It includes a title, a detailed message body, and replies from collaborators, all tied to the project for clear context and visibility, making it ideal for important discussions that need to be organized and easily referenced over time.
    Connector
  • Generate a structured, receipted context package for a new agent — the equivalent of soul.md + heartbeat.md + user.md but machine-queryable and backed by MemoryCrux records. Includes identity, operator context, active constraints, operating rhythms, knowledge briefing, and heartbeat schedule. Scope: minimal (identity + constraints), standard (all), comprehensive (standard + full knowledge).
    Connector
  • Get user context for adaptive conversation. Returns lifecycle stage and behavioral signals.
    Connector
  • Load skill content for selected skills and assemble into a context block for a specific IDE/runtime. Call after skill_loader_recommend to get the actual skill content.
    Connector
  • Full task context: task metadata, stages with status and weight, active blockers, linked artefacts (constraints, decisions, knowledge), recent log entries, and pinned master plan version. Assembles the full picture from PlanCrux and MemoryCrux.
    Connector
  • Check a code snippet against one or more policy packs. Returns violations with severity, governance context (CWE, MITRE, regulatory), and line numbers.
    Connector