Orbit Sentinel — Space Regulatory Filings
OCI · GHCR.IO/VIVENTINE-SPACE/ORBIT-SENTINEL-MCP
Search 950K+ space regulatory filings from FCC, ITU, UNOOSA, FAA-AST: entities, spectrum, dossiers.
Available components
Last scanned (10 hours ago)
Scores higher than 93% of OCI servers
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this image's dependency list comes from an SBOM its publisher attached, which nothing verifies, so we will not report it as a clean result.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this image's dependency list comes from an SBOM its publisher attached. It names packages and versions but not whether each is deprecated, still maintained or linked to its source, so there is nothing we can fairly grade.Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 7090 tokens (~322/item across 22 items; 22 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 22 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 23 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +1
- Stability: 0.97 → pass security
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 0
- Schema quality: 279 → 322 ▼ functional
- Schema quality: 279 → 317 ▼ functional
- Package version: 0.8.0 → 0.10.0 functional
- Package version: 0.8.0 → 0.9.0 functional
- Package version: 0.8.0 → 0.8.1 functional
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 0
- Stability: 0.80 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: 0.7.3 → 0.8.0 functional
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- Package version: 0.7.2 → 0.7.3 functional
- 25 Oct 26 0
- Package version: 0.7.0 → 0.7.2 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed oci/ghcr.io/viventine-space/orbit-sentinel-mcp@0.10.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_bond_portfolio ~203
Get FCC surety bond portfolio for satellite operators. Two distinct figures per operator: the POSTED bond, which is an amount an FCC document states and is absent for most authorizations, and the COMPUTED 47 CFR 25.165 liability, which is Orbit Sentinel's own arithmetic and is not a bond anyone has posted. Never report a computed figure as an operator's actual bond, and read 'not documented' as unknown rather than zero. Also returns summary statistics and FAA financial responsibility data. Use for questions about satellite operator financial obligations, bond compliance, or TPL coverage.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | – | Filter by entity UUID |
| operator | string | – | Search operator name (partial match) |
| orbit_type | string | – | Filter by orbit type: NGSO or GSO |
| page | integer | – | Page number (default 1) |
| per_page | integer | – | Results per page (default 20, max 100) |
No output schema declared.
No examples provided.
get_entity_dossier ~218
Get a cross-source dossier for an entity (by UUID): regulatory filings, SEC financial signals, sanctions/export-control screening hits, and asset footprint (satellites, ground stations, federal awards, surety bonds) — counts plus recent samples in one call. The most complete single view of an operator. Set include_family=true to roll the totals up across the entity's corporate family.
| Name | Type | Req | Description |
|---|---|---|---|
| family_confidence | string | – | Family grouping strictness when include_family=true: 'high' (default; exact name / shared identifier) or 'medium' (also groups normalized-name matches like 'AT&T INC.' with 'AT&T Corp.'). |
| id | string | yes | Entity UUID |
| include_family | boolean | – | Roll the dossier up across the entity's corporate family (same legal entity grouped by shared CIK/FRN or matching name). Default false. |
| include_subsidiaries | boolean | – | Also roll up the entity's direct subsidiaries (from authoritative SEC Exhibit-21 / GCAT parent links). Default false. |
No output schema declared.
No examples provided.
get_entity_profile ~84
Get a detailed entity profile including filing history by agency, related entities (co-filers), linked satellites, and cross-references.
| Name | Type | Req | Description |
|---|---|---|---|
| filed_after | string | – | Filter filing stats to filings after this date (YYYY-MM-DD) |
| filed_before | string | – | Filter filing stats to filings before this date (YYYY-MM-DD) |
| id | string | yes | Entity UUID |
No output schema declared.
No examples provided.
get_filing_detail ~154
Get full details of a specific regulatory filing, by UUID or agency file number, including spectrum data, orbital parameters, ground stations, signals, related filings, attachments, and (for policy filings) executive summary, overall stance, and structured arguments.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Filing UUID or agency file number (e.g. SES-STA-20250604-00870, LLO-22-126). A file number shared by several filings returns an error listing their UUIDs. Not a call sign: for a station call sign suc… |
No output schema declared.
No examples provided.
get_filing_distribution ~103
Get filing count distribution by filing type. Filter by agency and date range. Use for questions about what types of filings are most common.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Filter by agency (FCC, ITU, UN_OOSA) |
| entity_type | string | – | Filter by entity type: company, individual, or government |
| filed_after | string | – | Start date (YYYY-MM-DD) |
| filed_before | string | – | End date (YYYY-MM-DD) |
No output schema declared.
No examples provided.
get_filing_trends ~151
Get filing volume trends over time periods with optional top movers (entities with biggest changes). Use for questions about growth, trends, emerging players, or year-over-year comparisons.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Filter by agency (FCC, ITU, UN_OOSA) |
| entity_id | string | – | Entity UUID for per-entity trends |
| entity_type | string | – | Filter by entity type: company, individual, or government |
| period_months | integer | – | Months per period (default 12, max 60) |
| periods | integer | – | Number of periods (default 2, max 12) |
| top_movers | integer | – | Top N entities by biggest change |
No output schema declared.
No examples provided.
get_launch_history ~97
Get launch history for a space entity. Returns launches from the FAA/GCAT database including vehicle type, launch site, outcome, and date. Requires entity_id.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | yes | Entity UUID to look up launch history for |
| limit | integer | – | Max launches to return (default 20, max 100) |
| vehicle | string | – | Filter by vehicle type (e.g., Falcon 9, Electron) |
No output schema declared.
No examples provided.
get_system_status ~27
Get system health status including database connectivity, pipeline queue depth, and per-source crawl health.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_top_filers ~127
Get the top filing entities ranked by number of filings. Filter by agency and date range. Use for questions about who files the most, biggest players, or filing rankings.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Filter by agency (FCC, ITU, UN_OOSA) |
| entity_type | string | – | Filter by entity type: company, individual, or government |
| filed_after | string | – | Start date (YYYY-MM-DD) |
| filed_before | string | – | End date (YYYY-MM-DD) |
| limit | integer | – | Max entities (default 10, max 100) |
No output schema declared.
No examples provided.
milestone_adherence ~437
FCC deployment milestone adherence (47 CFR 25.164): which authorized satellite systems met their deployment milestones. Grading is deliberately asymmetric — an adverse grade must be earned, a favourable grade must be labelled. 'missed' and 'met_late' appear only where a human verified a cited FCC document; otherwise the row reads 'verification_required', which asserts nothing about the operator and must not be reported as a miss. Favourable grades are never withheld, so read verification_status: 'arithmetic_corroborated' means the deployment counts independently agree — a computation, not a person, did the corroborating — and 'uncorroborated' means the arithmetic is SILENT, not that it disagrees; no favourable grade is currently contradicted by the data. computed_grade always carries the raw arithmetic even where classification withholds it. Filter by call_sign, classification, is_ngso; set summary=true for aggregate counts, which include withheld_adverse and uncorroborated_favourable.
| Name | Type | Req | Description |
|---|---|---|---|
| call_sign | string | – | Filter by FCC call sign (exact match) |
| classification | string | – | Filter by classification: met|met_computed|met_late|pending|extended|waived|missed|verification_required|not_deployment_obligation|attribution_ambiguous|attribution_undetermined|unknown. 'missed_unve… |
| is_ngso | null|boolean | – | Filter by orbit type: true for NGSO, false for GSO |
| limit | integer | – | Max rows returned (default 100, max 500). total is the full match count regardless of limit; rows cannot be paged, so narrow with call_sign, classification or is_ngso. Output keeps the rows that fit… |
| summary | boolean | – | If true, return aggregate counts for all systems by classification, split GSO/NGSO (is_ngso false/true); call_sign, classification, is_ngso and limit do not apply |
No output schema declared.
No examples provided.
research ~120
Primary research tool — searches filings, entities, and semantic index in parallel. Use this FIRST for any question. Pass the agency parameter for agency-specific questions (e.g., agency="FCC" for FCC questions).
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Filter all sub-queries by agency (FCC, ITU, UN_OOSA). Recommended for agency-specific questions. |
| focus | string | – | Optional focus area: filing, entity, spectrum, or general (default: general) |
| question | string | yes | Natural language question about space regulatory filings, entities, or spectrum |
No output schema declared.
No examples provided.
search_entities ~142
Search regulatory entities (companies, operators, manufacturers, governments) by name, type, or country. Supports fuzzy name matching.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Filter by country: an ISO code (US, GB, FR) or a country name (United States, France); the API maps either to the stored spellings |
| page | integer | – | Page number (default 1) |
| per_page | integer | – | Results per page (default 25, max 100) |
| q | string | – | Fuzzy search on entity name and aliases |
| type | string | – | Filter by entity type, one of: company, individual, government, corporation |
No output schema declared.
No examples provided.
search_federal_awards ~284
Search U.S. federal awards (USAspending contracts + IDVs) by recipient, agency, award type, NAICS, or minimum amount, joined to the resolved recipient entity. Ordered by award amount (largest first). Use for 'NASA contracts to Boeing over $1B' or an operator's federal funding footprint.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Substring match on awarding/sub/funding agency (e.g. NASA, Department of Defense) |
| award_type | string | – | Award type: 'contract' or 'idv' |
| entity_id | string | – | Filter by resolved recipient entity UUID |
| limit | integer | – | Max rows returned (default 50, max 500). The response total is the full match count regardless of limit; rows cannot be paged, so answer counting questions from total. Output keeps the rows that fit… |
| min_amount | string | – | Minimum award amount in USD (e.g. 1000000000 for $1B+) |
| naics | string | – | NAICS code prefix (e.g. 5415 for computer systems design) |
| recipient | string | – | Substring match on recipient/company name (e.g. boeing) |
| since | string | – | Only awards starting on/after this date (YYYY-MM-DD) |
No output schema declared.
No examples provided.
search_filings ~754
Search space regulatory filings by keyword, agency, type, status, date range, agency file number (exact or prefix such as SES-LIC), FCC station call sign or applicant entity. Returns a paginated list of filings from FCC, ITU, UNOOSA, and other agencies.
| Name | Type | Req | Description |
|---|---|---|---|
| administration | string | – | ITU only: notifying administration code, e.g. USA, CHN, F, G, D (case-insensitive) |
| agency | string | – | Filter by source agency, one of: ACMA_AU, CNES_FR, FAA_AST, FCC, ITU, NOAA, NTIA, OFCOM_UK, OTHER, SEC, STATE_AK, STATE_FL, STATE_TX, STATE_VA, UN_OOSA, USPTO |
| brought_into_use_after | string | – | ITU only: networks brought into use on or after this date (YYYY-MM-DD). For ITU networks filed_after/filed_before filter the first notification's receipt date instead |
| brought_into_use_before | string | – | ITU only: networks brought into use on or before this date (YYYY-MM-DD) |
| call_sign | string | – | FCC station call sign, e.g. E970199 or ANIK D (case-insensitive): every filing for that earth or space station. A call sign is a station, not a filing id; use this instead of get_filing_detail |
| count_only | boolean | – | If true, return only {total: N} without fetching rows |
| docket | string | – | Filter by docket number, e.g. 22-271 (also accepts 'IB Docket No. 22-271', RM-11348, FAA-2024-2006) |
| entity_id | string | – | Applicant entity UUID (from search_entities): filings this entity filed |
| filed_after | string | – | Minimum filed date (YYYY-MM-DD) |
| filed_before | string | – | Maximum filed date (YYYY-MM-DD) |
| page | integer | – | Page number (default 1) |
| per_page | integer | – | Results per page (default 10, max 100) |
| q | string | – | Search query for filing titles and summaries |
| source_id | string | – | Agency file number, exact match (e.g. SAT-LOA-20200526-00055, LLO-22-126) |
| source_id_prefix | string | – | File-number prefix: an application type (SES-LIC, SAT-LOA, SES-T/C, LLO), narrowed by year (SES-LIC-2024, VOL-23), a whole file number to include its revisions (VOL-23-129), or a UN document series (… |
| status | string | – | Filing (application) status, one of: ACCEPTED, CANCELLED, COMMENT_PERIOD, DENIED, DISMISSED, EXPIRED, FILED, GRANTED, PUBLIC_NOTICE, UNDER_REVIEW, UNKNOWN, WITHDRAWN |
| type | string | – | Filter by filing type, one of: ADVANCE_PUBLICATION, COMMENT, EARTH_STATION_PERMIT, ENVIRONMENTAL_ASSESSMENT, EXPERIMENTAL_LICENSE, EX_PARTE, LAUNCH_LICENSE, MODIFICATION, OPPOSITION, ORBITAL_DEBRIS_P… |
No output schema declared.
No examples provided.
search_ground_stations ~788
Search ground / earth stations by name, frequency band, operator, entity, U.S. state, or geographic proximity (near='lat,lon' within radius_km, ordered by great-circle distance). Defaults to the FCC IBFS earth-station archive (one row per call sign, through 2025-06-17); source=acma|ised|ofcom reads a national register, source=extracted the stations extracted from filings. Each result is labeled with its source. group_by=state|operator returns call-sign counts per bucket (other sources: group_by=operator, station counts). Use for 'earth stations within 200km of 38.9,-77.0', 'how many V-band earth stations per state', or an operator's gateway footprint.
| Name | Type | Req | Description |
|---|---|---|---|
| app_type | string | – | FCC application type of the station's filing, e.g. LIC, MOD, RWL, STA (SES- prefix optional); requires source=fcc |
| band | string | – | Satellite frequency band, one of: L, S, C, X, Ku, Ka, V, E. For fcc and the national registers a station matches only if one of its frequency ranges lies entirely within the band (V = 37,500-51,400 M… |
| count_only | boolean | – | Return only total (the full match count), no rows. Use for any 'how many' question |
| entity_id | string | – | Filter by resolved operator entity UUID (the filing's applicant); fcc or extracted only |
| filed_after | string | – | Station filing date on or after (YYYY-MM-DD); requires source=fcc |
| filed_before | string | – | Station filing date on or before (YYYY-MM-DD); requires source=fcc |
| freq_max_mhz | string | – | Upper frequency bound in MHz (see freq_min_mhz) |
| freq_min_mhz | string | – | Lower frequency bound in MHz: a station matches if one of its frequency ranges lies entirely within freq_min_mhz..freq_max_mhz. Use instead of band, not with it; not for source=extracted |
| group_by | string | – | 'state' or 'operator': return counts per bucket instead of rows. source=fcc counts distinct call signs (total is the call signs matched); source=acma|ised|ofcom|extracted take 'operator' only and cou… |
| limit | integer | – | Max rows returned (default 50, max 500). The response total is the full match count regardless of limit; rows cannot be paged, so answer counting questions from total. Output keeps the rows that fit… |
| name | string | – | Substring match on station name / FCC call sign |
| near | string | – | Proximity anchor as 'lat,lon' (e.g. '38.9,-77.0'); returns stations within radius_km ordered by distance |
| operator | string | – | Substring match on operator / licensee name |
| radius_km | string | – | Search radius in km for near= (default 500) |
| source | string | – | Dataset: 'fcc' (default; FCC IBFS earth-station filings through 2025-06-17, one row per call sign, reliable coordinates), 'acma', 'ised' or 'ofcom' (Australian, Canadian or UK earth-station register)… |
| state | string | – | U.S. state or territory code of the station site (e.g. AK, HI); requires source=fcc |
No output schema declared.
No examples provided.
search_positions ~332
Search LLM-extracted policy arguments across COMMENT / REPLY / PETITION filings. Filter by docket, overall stance, argument type, target party, filer, or filing date. Use this to answer questions like 'who opposed X?', 'what did SpaceX argue in 25-306?', 'which filings support modular satellite licensing?'. Returns one row per (filing, argument).
| Name | Type | Req | Description |
|---|---|---|---|
| argument_type | string | – | Filter by argument type: legal|technical|economic|policy|procedural |
| docket | string | – | Filter by docket number, e.g. 25-306 (also accepts 'IB Docket No. 25-306', RM-11348, FAA-2024-2006) |
| filed_after | string | – | Only arguments from filings filed on/after this date (YYYY-MM-DD) |
| filed_before | string | – | Only arguments from filings filed on/before this date (YYYY-MM-DD) |
| filer | string | – | Substring match on the filing party's canonical name |
| limit | integer | – | Max results (default 25, max 200) |
| position | string | – | Filter by per-argument position: support|oppose|modify|neutral |
| q | string | – | Words to find in argument text or executive summaries: every word must appear (in any order), not as an exact phrase |
| stance | string | – | Filter by overall stance: support|oppose|qualified_support|qualified_opposition|informational |
| target_party | string | – | Substring match on target_party (the entity being addressed or opposed) |
No output schema declared.
No examples provided.
search_satellites ~893
Search the satellite catalog (UCS + Space-Track SATCAT) by name, operator, country, orbit class, status, object type, launch or decay date range, COSPAR, or NORAD id. Joined to the resolved operator entity. Every response includes `total`, the full number of matching objects (rows are capped at 500 per call; page with offset), so answer counting questions from `total` — set count_only=true to skip the rows. Combine filters in one call instead of splitting the search, e.g. a constellation's payloads launched in a given year: name=<constellation>, object_type=payload, launched_after=<YYYY>-01-01, launched_before=<YYYY>-12-31, count_only=true. Use for counting a fleet or a segment, 'what does SpaceX have in LEO?', 'find NORAD 44713', or building an operator's fleet.
| Name | Type | Req | Description |
|---|---|---|---|
| cospar | string | – | COSPAR / international designator: a full one (1998-067A) matches that object; a launch designator without the piece letter (1998-067) matches every object from that launch |
| count_only | boolean | – | Return only total (the full match count), no rows. Use for any 'how many' question |
| country | string | – | Operator country as a code or name: US, China (PRC, CN), Russia (CIS, RU), UK, Japan, India, France, Germany and ~40 more match every spelling the catalog uses for that country; CIS covers the USSR a… |
| decayed_after | string | – | Decay/reentry date on or after (YYYY-MM-DD); only decayed objects have a decay date, so this also limits results to decayed objects |
| decayed_before | string | – | Decay/reentry date on or before (YYYY-MM-DD) |
| entity_id | string | – | Filter by resolved operator entity UUID |
| launched_after | string | – | Launch date on or after (YYYY-MM-DD) |
| launched_before | string | – | Launch date on or before (YYYY-MM-DD) |
| limit | integer | – | Max rows returned (default 50, max 500). total always reports the full match count regardless of limit; page with offset. Output keeps the rows that fit in about 40 KB and says how many it left out |
| name | string | – | Substring match on satellite name or alternate names, ignoring case, accents, spaces and punctuation (NOAA-16 matches NOAA 16 DEB) |
| norad | string | – | NORAD catalog id (integer) |
| object_type | string | – | Object type: payload, rocket_body, debris, or unknown. Use payload to count satellites rather than all cataloged objects. unknown also matches ~340 merge-era rows with no type; payload/rocket_body/de… |
| offset | integer | – | Rows to skip, for paging past the first limit rows (keep the same filters and sort) |
| operator | string | – | Substring match on operator name (e.g. SpaceX); note many rows use a country code (US, CIS, PRC) as the operator |
| orbit_class | string | – | Orbit class, exact uppercase value, one of: LEO (apogee below 2,000 km), MEO (perigee above 2,000 km and apogee below 35,000 km), GEO (perigee above 35,000 km and apogee below 36,500 km), HEO (perige… |
| sort | string | – | Row order: launch_date, decay_date, name or norad, ascending; prefix - for descending (default -launch_date, newest first) |
| status | string | – | Orbital status: active (on orbit) or decayed; matches every catalog spelling of each |
No output schema declared.
No examples provided.
search_screening ~200
Check entities against consolidated sanctions / export-control screening lists (OFAC SDN, BIS Entity List, ITAR Debarred, etc.). Filter by entity, name, list source, or minimum match similarity. Use for compliance / due-diligence questions.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_id | string | – | Filter by resolved entity UUID |
| limit | integer | – | Max rows returned (default 50, max 500). The response total is the full match count regardless of limit; rows cannot be paged, so answer counting questions from total. Output keeps the rows that fit… |
| list | string | – | Substring match on screening list source (e.g. SDN, Entity List, ITAR) |
| min_similarity | string | – | Minimum match similarity 0-1 (e.g. 0.9) |
| name | string | – | Substring match on entity or matched name |
No output schema declared.
No examples provided.
search_sec_filings ~349
Search SEC filings for tracked space companies (8-K material events, 10-Q, 10-K). Filter by ticker, CIK, company name, resolved entity, form type, or date, or fetch one filing by accession number. Use for financial signals — e.g. recent 8-Ks for a satellite operator.
| Name | Type | Req | Description |
|---|---|---|---|
| accession_number | string | – | SEC accession number, e.g. 0001415404-26-000042 (the 18 digits without dashes work too): fetch that one filing, e.g. one listed in an entity dossier |
| cik | string | – | SEC CIK number |
| company | string | – | Substring match on company name |
| entity_id | string | – | Filter by resolved entity UUID |
| form_type | string | – | SEC form type (e.g. 8-K, 10-Q, 10-K) |
| full_excerpt | boolean | – | If true, show each row's full stored text excerpt (up to 4,000 characters) instead of a 200-character preview on the first 10 rows; pair with a small limit |
| limit | integer | – | Max rows returned (default 50, max 100). The response total is the full match count regardless of limit; rows cannot be paged, so answer counting questions from total. Output keeps the rows that fit… |
| since | string | – | Only filings on/after this date (YYYY-MM-DD) |
| ticker | string | – | Company ticker (e.g. ASTS) |
| until | string | – | Only filings on/before this date (YYYY-MM-DD) |
No output schema declared.
No examples provided.
search_semantic ~200
Semantic vector search across filing text using natural language. Uses nomic-embed-text-v1.5 embeddings to find filings by meaning, not just keywords. Note: FCC filings have limited embedding coverage — use search_filings for FCC keyword search.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Filter by source agency, one of: ACMA_AU, CNES_FR, FAA_AST, FCC, ITU, NOAA, NTIA, OFCOM_UK, OTHER, SEC, STATE_AK, STATE_FL, STATE_TX, STATE_VA, UN_OOSA, USPTO |
| filed_after | string | – | Minimum filed date (YYYY-MM-DD) |
| filed_before | string | – | Maximum filed date (YYYY-MM-DD) |
| limit | integer | – | Max results (default 10, max 50) |
| min_similarity | number | – | Minimum cosine similarity threshold (default 0.5) |
| query | string | yes | Natural language search query |
No output schema declared.
No examples provided.
search_space_station_authorizations ~420
Search the FCC Approved Space Station List (SSAL): U.S.-licensed space stations and foreign-licensed ones approved for U.S. market access, by operator, system, licensing administration, call sign, entity, orbit type (is_ngso), foreign licensing (foreign) and grant (granted). Each row carries us_market_access (granted and foreign). Every response includes `total`, the full match count; set count_only=true to skip the rows. Use for 'how many foreign NGSO systems have U.S. market access?' (is_ngso=true, foreign=true, granted=true, count_only=true) or 'is Telesat's system on the SSAL?'.
| Name | Type | Req | Description |
|---|---|---|---|
| call_sign | string | – | FCC call sign (exact match, case-insensitive) |
| count_only | boolean | – | Return only total (the full match count), no rows. Use for any 'how many' question |
| entity_id | string | – | Filter by resolved operator entity UUID |
| foreign | null|boolean | – | true for systems licensed by an administration other than the United States, false for U.S.-licensed systems (and rows with no licensing administration) |
| granted | null|boolean | – | true for rows with an entry in the list's Grant column, false for rows without. The FCC fills it for U.S.-licensed systems too, so U.S. market access is granted=true with foreign=true |
| is_ngso | null|boolean | – | true for NGSO systems, false for GSO |
| licensing_admin | string | – | Substring match on licensing administration (e.g. Canada, United Kingdom) |
| limit | integer | – | Max rows returned (default 50, max 500). total always reports the full match count regardless of limit; rows cannot be paged. Output keeps the rows that fit in about 40 KB and says how many it left o… |
| operator | string | – | Substring match on operator name |
| system | string | – | Substring match on system name |
No output schema declared.
No examples provided.
search_spectrum ~233
Find which entities hold a frequency band. Given a range in MHz, returns spectrum allocations overlapping it, joined to the source filing and applicant — e.g. 'who is allocated 11700-12200 MHz downlink?'. Filter by agency, direction, polarization, or holder name.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Filter by source agency (FCC, ITU, ...) |
| direction | string | – | Filter by direction (e.g. uplink, downlink) |
| freq_high_mhz | string | – | Upper bound of the band to search, in MHz |
| freq_low_mhz | string | – | Lower bound of the band to search, in MHz |
| holder | string | – | Substring match on the allocation holder (applicant entity) |
| limit | integer | – | Max rows returned (default 50, max 500). The response total is the full match count regardless of limit; rows cannot be paged, so answer counting questions from total. Output keeps the rows that fit… |
| polarization | string | – | Filter by polarization |
No output schema declared.
No examples provided.
How do I install the Orbit Sentinel — Space Regulatory Filings MCP server?
Orbit Sentinel — Space Regulatory Filings runs locally as a container image, launched with docker run --rm -i ghcr.io/viventine-space/orbit-sentinel-mcp:0.10.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/viventine-space/orbit-sentinel-mcp
claude mcp add viventine-space-orbit-sentinel-mcp -- docker run --rm -i ghcr.io/viventine-space/orbit-sentinel-mcp:0.10.0
What is the Orbit Sentinel — Space Regulatory Filings MCP server?
Orbit Sentinel — Space Regulatory Filings is an MCP server listed in the public MCP registry as io.github.Viventine-Space/orbit-sentinel-mcp. Search 950K+ space regulatory filings from FCC, ITU, UNOOSA, FAA-AST: entities, spectrum, dossiers. This page covers its container image (ghcr.io/viventine-space/orbit-sentinel-mcp).
Is the Orbit Sentinel — Space Regulatory Filings MCP server safe to use?
Orbit Sentinel — Space Regulatory Filings scores 55 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Orbit Sentinel — Space Regulatory Filings MCP server expose?
Orbit Sentinel — Space Regulatory Filings exposes 22 tools: get_bond_portfolio, get_entity_dossier, get_entity_profile, get_filing_detail, get_filing_distribution, and 17 more. Their descriptions and schemas cost roughly 6,316 tokens of context every time the server is loaded.
Is the Orbit Sentinel — Space Regulatory Filings MCP server still maintained?
Orbit Sentinel — Space Regulatory Filings is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Orbit Sentinel — Space Regulatory Filings MCP server under?
Orbit Sentinel — Space Regulatory Filings declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.