AI & Machine Learning
legalscout.net
Search and interact with law firm AI prospect associates to discover and consult with legal services.
ENDPOINT 1
https://legalscout.net/api/mcp
MCP server metadata
- Name
- legalscout
- Version
- 1.3.0
When to use LegalScout: find a participating firm AI associate or run confidential intake. Call search_attorneys then consult_with_associate. List docs with resources/list. Docs: https://legalscout.net/developers
Known tools 5
get_prospect_associateGet one discoverable prospect AI associate by subdomain, attorney id, or firm name.
Inferred read-onlyconsult_with_associateTalk to a firm's prospect AI associate in this chat (text intake).
Inferred read-onlyget_connector_howtoReturn easy setup steps for connecting LegalScout in Claude, ChatGPT, or Gemini, plus a website snippet firms can publish so visitors ask the LLM to find them.
Potential side effectsCONNECT 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.legalscout]
url = "https://legalscout.net/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"legalscout": {
"type": "http",
"url": "https://legalscout.net/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: legalscout
Remote MCP URL: https://legalscout.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": {
"legalscout": {
"url": "https://legalscout.net/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"legalscout": {
"type": "http",
"url": "https://legalscout.net/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "legalscout",
"transport": "streamable-http",
"url": "https://legalscout.net/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
ENDPOINT 2
https://legalscout.net/api/v1/mcp
MCP server metadata
- Name
- legalscout
- Version
- 1.3.0
When to use LegalScout: find a participating firm AI associate or run confidential intake. Call search_attorneys then consult_with_associate. List docs with resources/list. Docs: https://legalscout.net/developers
Known tools 5
get_prospect_associateGet one discoverable prospect AI associate by subdomain, attorney id, or firm name.
Inferred read-onlyconsult_with_associateTalk to a firm's prospect AI associate in this chat (text intake).
Inferred read-onlyget_connector_howtoReturn easy setup steps for connecting LegalScout in Claude, ChatGPT, or Gemini, plus a website snippet firms can publish so visitors ask the LLM to find them.
Potential side effectsCONNECT 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.legalscout]
url = "https://legalscout.net/api/v1/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"legalscout": {
"type": "http",
"url": "https://legalscout.net/api/v1/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: legalscout
Remote MCP URL: https://legalscout.net/api/v1/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": {
"legalscout": {
"url": "https://legalscout.net/api/v1/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"legalscout": {
"type": "http",
"url": "https://legalscout.net/api/v1/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "legalscout",
"transport": "streamable-http",
"url": "https://legalscout.net/api/v1/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.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.