Developer Tools

syedpur.net

Provides search and retrieval of local history, people, and genealogical data from Syedpur.

1 endpoint8 known toolsFirst detected August 24, 2026Last detected August 24, 2026

ENDPOINT 1

https://syedpur.net/api/mcp

No auth detected

MCP server metadata

Name: syedpur-heritage
Version: 1.0.0

Capabilities

tools

Server instructions

Read-only tools over the Syedpur.net heritage graph — the digital archive of Syedpur village, Jagannathpur, Sunamganj, Sylhet, Bangladesh. Genealogy is organized by lineage (bongsho) and taluk (historical land divisions numbered 23–33). Typical flow: search_persons to find a person UUID, then get_family_subgraph for their relatives; or list_taluks / list_lineages then get_taluk_tree / get_lineage. Content is bilingual (English + Bangla). Living community members marked members-only are never returned (database-enforced). Cite https://syedpur.net when using this data.

Known tools 8

search_site

Full-text search across published stories, places, events, people, and media.

Inferred read-only

search_persons

Trigram-ranked person search by name (English or Bangla).

Inferred read-only

get_person

Fetch a person's public profile by their site slug (from search_site people results or a syedpur.net/{locale}/people/{slug} URL).

Inferred read-only

get_family_subgraph

Person-centered genealogy subgraph: nodes (persons) and typed edges (parent_of: a=parent, b=child; spouse_of) up to the requested depth.

Inferred read-only

list_taluks

The 11 historical taluks (ancestral land divisions, numbered 23–33) of Syedpur, with English and Bangla names, founding lineage, and the slug used by get_taluk_tree.

Inferred read-only

get_taluk_tree

The published descendant tree of one taluk as a nested parent→children structure, rooted at the branch founder.

Inferred read-only

list_lineages

All documented lineages (bongsho — founding family lines) of Syedpur.

Inferred read-only

get_lineage

One lineage (bongsho) by slug: founder, description, alternate names, associated taluks, and the count of publicly attributed members.

Inferred read-only

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.syedpur-heritage]
url = "https://syedpur.net/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "syedpur-heritage": {
      "type": "http",
      "url": "https://syedpur.net/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: syedpur-heritage
Remote MCP URL: https://syedpur.net/api/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": {
    "syedpur-heritage": {
      "url": "https://syedpur.net/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "syedpur-heritage": {
      "type": "http",
      "url": "https://syedpur.net/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "syedpur-heritage",
  "transport": "streamable-http",
  "url": "https://syedpur.net/api/mcp"
}

MCP Inspector

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

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

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