LinkCensus

LinkCensus agent clients

Release-candidate source for the LinkCensus REST client/CLI and local stdio MCP gateway. This export contains only the two client packages, their source, tests, notices, license and release metadata. It contains no application server, graph, customer state, deployment configuration or repository history. The public source repository is linkcensus-agent-clients. The hosted MCP endpoint is live at https://linkcensus.com/mcp using Streamable HTTP. Sign in at your account and configure your personal key in a private Authorization: Bearer YOUR_LINKCENSUS_API_KEY header. Use a client that supports a custom Authorization header. See the MCP setup guide and API documentation.

Public PyPI package releases remain pending; the local package versions below are separate from hosted availability.

Packages

Free access includes 5 neighborhood lookups per account per UTC calendar month, with up to 5 candidate rows per lookup. REST, CLI and MCP share that counter; rotation does not reset it. Editions and domain resolution do not spend monthly neighborhood attempts but still require authentication and execution admission. Candidates are not independently confirmed competitors; retain edition, provenance, truncation and quota notes. The website ledger and VerifiedPricing budgets are separate. No request triggers a crawl or retries automatically.

The hosted service uses personal bearer keys. The local stdio gateway uses HTTPS REST and remains available as a separate source package. Linux/Python 3.12 is tested for local stdio; other source-supported Python 3.10+/POSIX combinations need acceptance, and Windows is unsupported. See each package's transport limits.

Candidate installation

Public package-index installation is not available from this release candidate. A placeholder wheelhouse path below is not evidence of a public package or downloadable bundle. Use a separately reviewed isolated environment and complete wheelhouse:

python3 -m venv .venv-linkcensus.venv-linkcensus/bin/python -m pip install --no-index \  --find-links /path/to/reviewed-wheelhouse \  linkcensus-client==0.1.0 linkcensus-mcp==0.1.0 mcp==2.3.0.venv-linkcensus/bin/linkcensus --version.venv-linkcensus/bin/linkcensus-mcp --version

Provide a key through the private environment or owned regular mode-0600 configuration. Never put it in arguments, public examples or repository files. linkcensus configure saves an already provisioned LINKCENSUS_API_KEY; it does not sign in or issue keys. See client setup and the secret-free launcher template.

Local source checks

No installation or backend is needed for the client package's bounded unit and loopback tests:

cd packages/linkcensus-clientPYTHONDONTWRITEBYTECODE=1 PYTHONPATH=src python3 -m unittest discover -s tests -v

For gateway checks, use a reviewed separate environment with the exact pinned SDK and both distributions installed; add the two source directories to its PYTHONPATH, then run the gateway tests. Tests use synthetic credentials/fixtures, not production. The initial SDK installation and public-index clean-install acceptance are separate operations, not test side effects.

Distribution and security

The hosted endpoint is listed in the official MCP Registry. server.hosted.json contains the published manifest. The separate PyPI/stdio manifest remains a distribution candidate; public package-index publication and installation are pending.

Do not post credentials or private responses. Use private GitHub vulnerability reporting for security issues. This feature is enabled; no response-time commitment is promised. See the client policy and gateway policy.

Both packages retain their existing MIT licenses, copied unchanged to the root. Original VerifiedPricing and LinkCensus copyright notices are preserved. The gateway provenance note records the licensed transport adaptation; no new copyright attribution is invented.

EXPORT_ALLOWLIST.json names every exported file. EXPORT_MANIFEST.json binds all payload files except itself by SHA-256 and byte length; the private review receipt separately records the manifest's hash. No secret scan establishes that credentials can never exist: review the exact candidate and artifact before publication, and retain any reported synthetic-test classification.