Skip to main content
Glama
Caleb68864

Harrier

by Caleb68864
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
COURTLISTENER_TOKENNoOptional token for higher CourtListener API rate limits.
FAMILYSEARCH_ACCESS_TOKENNoOptional token to enable FamilySearch record-search API.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
generate_candidatesB

Generate ranked handle/email candidates from a person's name parts.

username_sweepB

Enumerate a username across social sites via Sherlock/Maigret.

email_reconB

Check whether an email is registered across free OSINT sources.

phone_lookupB

Scan a phone number with PhoneInfoga (free sources).

domain_harvestB

Harvest emails/hosts for a domain via theHarvester (free sources).

people_searchB

Look up a person on a free people-search site (consent-gated scrape).

court_searchB

Search CourtListener/RECAP federal court records for a person by name.

genealogy_searchC

Search FamilySearch records (maiden-name resolver; needs FAMILYSEARCH_ACCESS_TOKEN).

manual_assistB

Pre-filled search links for walled/gated free sources (makes no network call).

person_sweepC

Fan a person out across free OSINT sources; return tier-tagged findings.

investigateC

Bounded plan→collect→verify→refine investigation over all Harrier tools.

build_graphA

Build a provenance-stamped entity graph for a person.

    If ``findings`` (a list of Finding dicts from a prior sweep) is given, the
    graph is built from those — no new collection. Otherwise a verified
    ``person_sweep`` is run first. Returns the graph plus GraphML + Cypher
    exports and summary stats.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.4/5.0

Scored across 12 tools

Disambiguation5/5

Each tool targets a distinct resource or action: identifiers (username, email, phone, domain), sources (court, genealogy, people-search), and orchestration levels (person_sweep, investigate, build_graph). No two tools have overlapping purposes; even the broader tools are clearly differentiated by their descriptions.

Naming Consistency4/5

The majority of tools follow a target_action pattern (username_sweep, phone_lookup, court_search). A minority use verb_object (generate_candidates, investigate, build_graph), which is a minor deviation but all names are snake_case and readable.

Tool Count5/5

12 tools is well-scoped for an OSINT investigation server, covering identifier-specific lookups, person-specific searches, and higher-level orchestration without being redundant. Each tool earns its place.

Completeness4/5

The surface covers core OSINT workflows: identifier generation, username/email/phone/domain enumeration, court and genealogy searches, plus orchestration and graph building. Minor gaps like reverse image search or IP lookup exist but are not essential to the server's apparent person-centric focus.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources