General Tools

vladimirperovic.com

Provides general-purpose tools through the Model Context Protocol.

1 endpoint4 known toolsFirst detected October 15, 2026Last detected October 15, 2026

ENDPOINT 1

https://vladimirperovic.com/mcp

No auth detected

MCP server metadata

Name: vpaa-rules
Version: 1.3.0

Capabilities

tools

Server instructions

Use VPAA Rules as the sole source of regulatory facts for these answers. Decompose compound questions into canonical concepts/checks, preserve the original question, and extract only facts and measurements explicitly known from the client or project. Numeric measurements MUST include units. Never invent or silently convert an unknown unit. Use get_plan_context first when a Belgrade parcel or WGS84 point is known. Parcel input is refined against the complete cadastral polygon before direct-PGR parameters are promoted; coordinate input remains a point analysis. GIS-only planning values are informational. Only can_conclude_legal_parameters=true may support a final planning parameter; ambiguous boundaries and PDR/specific-plan precedence require manual or lower-order-plan review. Never calculate footprint or GFA from GIS-only coverage/FAR values. Development arithmetic is allowed only from verified planning parameters. Use search_rules for a focused legal question, check_project for selected checks, and audit_project for a broader pre-submission review. Only applicable_rules/findings with can_conclude_regulatory_requirement=true may support a legal assertion. possible_rules are prompts for missing information, not conclusions. If coverage is no_verified_answer or unverified_match_only, say that the verified database does not currently support a definitive answer and do not answer from model memory. In client-facing prose cite the returned regulation/article and never call no_detected_issue formal approval.

Known tools 4

search_rules

Find AI-verified informational rules for a focused legal/regulatory question.

Inferred read-only

check_project

Check known project facts/measurements against selected AI-verified informational rules.

Inferred read-only

audit_project

Run a broad pre-submission audit using all applicable AI-verified informational rules, optionally focused on concepts.

Inferred read-only

get_plan_context

Resolve a cadastral parcel or WGS84 point through public Beoland GIS and locally verified planning-zone records.

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.vpaa-rules]
url = "https://vladimirperovic.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "vpaa-rules": {
      "type": "http",
      "url": "https://vladimirperovic.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: vpaa-rules
Remote MCP URL: https://vladimirperovic.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": {
    "vpaa-rules": {
      "url": "https://vladimirperovic.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "vpaa-rules": {
      "type": "http",
      "url": "https://vladimirperovic.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "vpaa-rules",
  "transport": "streamable-http",
  "url": "https://vladimirperovic.com/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.