← Registry

Content Tools

agilegypsy.com

Provides tools to list and read AgileGypsy's offerings and website pages as Markdown, and to start or continue a project scoping conversation.

1 endpoint7 known toolsFirst detected September 29, 2026Last detected September 29, 2026

ENDPOINT 1

https://agilegypsy.com/mcp

No auth detected

MCP server metadata

Name
agilegypsy
Version
1.0.0
Capabilities
tools
Server instructions

AgileGypsy Labs (agilegypsy.com) is a South African consultancy: Web3 tokenomics, compliance and security, and AI systems and custom builds through its Labs practice. Use list_offers, list_pages and read_page to answer questions about what AgileGypsy does — those are the site's own published pages. To get a project quoted, hold a scoping conversation: start_scoping, then continue_scoping for each reply (show the assistant's reply to the person; answer from what the person tells you or from materials they point you at — never invent facts about their business), then build_scope (show the person the scope), then submit_scope. Nothing is sent to AgileGypsy until submit_scope, and it needs the person's name, email and explicit agreement to the consent statement in its description. Never send credentials, secrets, or personal information about anyone other than the person themselves.

Known tools 7

list_offers

List AgileGypsy's products and services: what each one is, who it is for, and its page on agilegypsy.com.

Inferred read-only
list_pages

List the agilegypsy.com pages available as Markdown, with their size in tokens.

Inferred read-only
read_page

Read one agilegypsy.com page as Markdown, by path — for example /services/tokenomics or /products/ai-support-agent.

Inferred read-only
start_scoping

Start a scoping conversation with AgileGypsy's scoping tool about a project the person wants quoted.

Inferred read-only
continue_scoping

Send the person's next message (an answer or a question) in a scoping conversation.

Potential side effects
build_scope

Turn the scoping conversation into a scope: the business, requirements, in and out of scope, assumptions, open questions, risks, phases, fitting offers and what AgileGypsy would need from the person.

Inferred read-only
submit_scope

Send the built scope, and the conversation it came from, to AgileGypsy for a quote.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.agilegypsy]
url = "https://agilegypsy.com/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "agilegypsy": {
      "type": "http",
      "url": "https://agilegypsy.com/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: agilegypsy
Remote MCP URL: https://agilegypsy.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "agilegypsy": {
      "url": "https://agilegypsy.com/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "agilegypsy": {
      "type": "http",
      "url": "https://agilegypsy.com/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "agilegypsy",
  "transport": "streamable-http",
  "url": "https://agilegypsy.com/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for agilegypsy.com was fetched 2026-10-01T05:13:42.677Z.

Trust status Trusted

agilegypsy.com is assessed as Trusted: Domain has an established technology history spanning over a year.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.