Evidence-first AI URL intelligence agent for crawling, entity resolution, social discovery, SEO, tec
URL Intelligence Agent turns any public URL into structured, evidence-backed intelligence. It goes beyond scraping and metadata extraction by combining safe crawling, entity resolution, social and contact discovery, domain and technology intelligence, SEO and security analysis, confidence scoring and source provenance. Built for developers and AI agents, it can investigate websites, identify people, companies, products and projects, discover relationships, monitor changes and generate structured outputs for RAG, automation and downstream applications. Run it through CLI, HTTP API or native MCP. AI reasoning is optional, the core intelligence pipeline works deterministically and can be fully self-hosted.
·
URL in. Identity, evidence and intelligence out.
Evidence-first public web intelligence for developers, AI agents, marketplaces, directories, research, monitoring and automation.
URL Intelligence Agent is one of the intelligence components used inside the HORNO ecosystem to understand public URLs, normalize entities, enrich profiles and listings, discover public relationships, evaluate web signals and prepare structured information for product workflows.
The complete agent architecture is available here as open source so developers can inspect it, self-host it, extend it and integrate the same evidence-first approach into their own applications and AI systems.
The two repositories are complementary and can be used independently.
If you need the complete intelligence layer — multi-page crawling, entity resolution, confidence and provenance, monitoring, reports, MCP, HTTP API, domain intelligence, technology detection, security/SEO analysis and optional AI reasoning — use URL Intelligence Agent.
If your application only needs fast, deterministic URL enrichment without the complete agent stack, use the lighter standalone project:
https://github.com/vpicciuolo/url-metadata-social-fetcher
It is the lightweight standalone option for applications that mainly need to take a public URL and extract reusable metadata such as titles, descriptions, Open Graph data, canonical URLs, images, social links and profile information with safety-focused fetching.
It is especially useful for:
| Choose | URL Intelligence Agent | URL Metadata & Social Profile Fetcher |
|---|---|---|
| Primary goal | Full evidence-first URL/entity intelligence | Fast lightweight URL enrichment |
| Multi-page intelligence | ✅ Deep crawl, sitemaps, important-page discovery | Focused lightweight extraction |
| Entity resolution | ✅ Confidence + evidence + provenance | Basic profile/metadata enrichment |
| SEO / security / trust / tech intelligence | ✅ | Lightweight metadata focus |
| Monitoring / snapshots / diffs | ✅ | Not the primary purpose |
| MCP server | ✅ | Not required |
| HTTP API / CLI agent workflows | ✅ | Library-oriented integration |
| Optional AI reasoning | ✅ | Deterministic-first lightweight use |
| Best for | AI agents, research, automation, intelligence platforms | Previews, directories, autofill, smart links, simple integrations |
Simple rule: if you only need to understand and enrich a URL, start with the lightweight repository. If you need to investigate, verify, connect, score, monitor and expose that intelligence to applications or AI agents, use this repository.
Quick Start · How it works · Capabilities · CLI · MCP · HTTP API · Docker · SDK · Reports · Monitoring · Configuration · Security · Support
A metadata parser can tell you a page title.
A crawler can collect pages.
A language model can summarize text.
URL Intelligence Agent connects those layers into a single evidence-first workflow.
Give it a public URL and it can answer:
What is this URL? What person, company, product, creator or project does it represent? Which public signals support that conclusion? What else is connected to it? What changed? What can an application or AI agent safely do with the result?
It combines deterministic collection, structured extraction, entity resolution, confidence scoring, provenance, crawling, infrastructure intelligence, monitoring and optional AI reasoning.
Do not ask an LLM to guess what deterministic public evidence can establish.AI is an enhancement layer. It is not required for the main intelligence pipeline.
git clone https://github.com/vpicciuolo/url-intelligence-agent.git
cd url-intelligence-agent
npm install
npm run buildnode dist/src/cli.js investigate https://example.comOr during development:
npm run dev -- investigate https://example.comnpm run devYou will get the full action menu with 39 interactive operations, including investigation, crawling, domain intelligence, social/contact discovery, SEO, security, monitoring, reports, MCP and API modes.
url-agent everywherenpm install -g github:vpicciuolo/url-intelligence-agentThen:
url-agent investigate https://example.com
url-agent seo https://example.com
url-agent technologies https://example.com
url-agent mcpflowchart LR
A[Public URL] --> B[URL safety + DNS validation]
B --> C[robots.txt + sitemap discovery]
C --> D[Bounded crawl]
D --> E[Optional JS render fallback]
D --> F[Metadata + JSON-LD + links]
E --> F
F --> G[Entity / social / contact resolution]
F --> H[Tech / brand / domain intelligence]
G --> I[Evidence + confidence + provenance]
H --> I
I --> J[SEO / security / quality / trust]
J --> K[Structured intelligence result]
K --> L[CLI]
K --> M[HTTP API]
K --> N[MCP]
K --> O[Reports / RAG / knowledge export]
K --> P[Snapshots / monitoring / webhooks]
K --> Q[Optional AI reasoning]Every major resolved field can carry:
{
"value": "Example Inc.",
"confidence": 0.97,
"method": "jsonld-name+og-site-name+page-title",
"sources": [
"https://example.com/",
"https://example.com/about"
]
}That provenance model is one of the central differences between this project and a basic scraper or model-only web summary.
The 1.0.0 runtime exposes 34 machine-callable core actions through the action registry. The interactive CLI combines them with reporting, watching, benchmarking, server and plugin operations for 39 menu choices. Plugins can extend the action surface further.
| Intelligence area | What the agent does |
|---|---|
| Safe URL collection | HTTP/HTTPS validation, DNS checks, private-network blocking, redirect re-validation, bounded time/bytes |
| Crawl & map | robots.txt, sitemaps, sitemap indexes, same-origin crawl, important-page discovery |
| Entity resolution | Person, creator, startup, organization, product, service, software, business, event and website inference |
| Metadata | title, description, canonical, Open Graph, headings, JSON-LD, images, favicons |
| Social discovery | normalized public social/profile links across supported networks |
| Contact discovery | public emails, phones, contact pages and public people/team signals |
| Domain intelligence | A/AAAA/MX/NS/TXT/CAA, SPF/DMARC hints, TLS certificate/protocol/cipher information |
| Technology detection | framework, CMS, ecommerce, analytics, payments, CDN, hosting and tooling fingerprints |
| Brand intelligence | name candidates, logo/favicon, social preview images, public handles, tagline/color hints |
| SEO audit | metadata, canonical, OG, structured data, sitemap, noindex and duplicate-title signals |
| Security posture | visible HTTP security headers, HTTPS/HSTS/CSP/frame/referrer/permissions signals |
| Quality signals | language, headings, text volume, timing, status, forms and image counts |
| Trust signals | explainable public transparency/trust indicators; not a fraud or legal determination |
| Entity graph | evidence-linked nodes and relationships between entity, profiles, contacts, pages and technologies |
| Competitor intelligence | public comparison/alternative context with evidence and confidence |
| API discovery | OpenAPI, Swagger, GraphQL, /api, docs, developer portals and .well-known references |
| Compliance signals | public privacy, cookie, terms, GDPR/CCPA, accessibility, security/trust references |
| Commerce intelligence | visible currencies/prices, pricing pages, ecommerce/subscription/marketplace language |
| Freshness | publication, modification and HTTP freshness hints |
| Link intelligence | internal/external links, external domains, bounded link health checking |
| Listing generation | directory/marketplace/ranking-board ready-to-review profile data |
| RAG export | citation-friendly clean documents with checksums and provenance |
| Knowledge export | structured facts prepared for downstream knowledge systems |
| Compare | compare entity type, socials, contacts, technologies, canonical host, SEO/trust |
| Batch workers | bounded concurrent investigations of multiple URLs |
| Monitoring | snapshots, diffs, continuous watch and optional webhook delivery |
| Rendering | optional Playwright or remote renderer fallback for JavaScript-heavy pages |
| AI reasoning | optional OpenAI-compatible evidence-only synthesis |
| Plugins | runtime enrichers and custom actions |
| MCP | native stdio MCP server exposing the runtime action registry |
| HTTP API | authenticated/rate-limited JSON action server |
| Reports | Markdown, standalone HTML and JSON output with attribution |
1. Full URL investigation
2. Safe URL probe / redirects
3. Domain + DNS + mail + TLS intelligence
4. Deep crawl + sitemap mapping
5. Render JavaScript page / browser fallback
6. Resolve entity + evidence graph
7. Find social profiles
8. Find public contacts + people
9. Technology fingerprinting
10. Brand intelligence
11. SEO audit
12. Security-header posture audit
13. Quality/accessibility/performance audit
14. Trust/transparency signals
15. Entity relationship graph
16. Competitor/comparison intelligence
17. Structured-data inventory
18. API / OpenAPI / GraphQL discovery
19. Privacy/compliance public signals
20. Team / people extraction
21. Commerce / pricing intelligence
22. Content freshness signals
23. Link graph / external-domain intelligence
24. Broken-link / URL health check
25. Generate marketplace/directory listing
26. RAG-ready document export
27. Knowledge/fact export with provenance
28. Generate Markdown + HTML + JSON reports
29. Compare two URLs
30. Batch enrichment worker
31. Create monitoring snapshot
32. Diff current URL against stored snapshot
33. Continuous scheduled watch + webhook
34. Optional AI evidence reasoning
35. Run reliability benchmark
36. Plugins / extension SDK
37. HTTP API server
38. MCP server
39. About & credits
0. Exit| Command | Example |
|---|---|
| Full investigation | url-agent investigate https://example.com |
| Safe probe | url-agent probe https://example.com |
| Domain/DNS/TLS | url-agent domain https://example.com |
| Deep crawl | url-agent crawl https://example.com |
| Render page | url-agent render https://example.com |
| Entity | url-agent entity https://example.com |
| Social profiles | url-agent socials https://example.com |
| Contacts/people | url-agent contacts https://example.com |
| Technologies | url-agent technologies https://example.com |
| Brand | url-agent brand https://example.com |
| SEO | url-agent seo https://example.com |
| Security | url-agent security https://example.com |
| Quality | url-agent quality https://example.com |
| Trust | url-agent trust https://example.com |
| Entity graph | url-agent graph https://example.com |
| Competitors | url-agent competitors https://example.com |
| Structured data | url-agent structured https://example.com |
| API discovery | url-agent apis https://example.com |
| Compliance signals | url-agent compliance https://example.com |
| People/team | url-agent people https://example.com |
| Commerce | url-agent commerce https://example.com |
| Freshness | url-agent freshness https://example.com |
| Link intelligence | url-agent links https://example.com |
| Link health | url-agent check-links https://example.com --limit 100 |
| Generate listing | url-agent listing https://example.com |
| RAG export | url-agent rag https://example.com |
| Knowledge export | url-agent knowledge https://example.com |
| Report | url-agent report https://example.com --out report |
| Compare | url-agent compare https://example.com https://example.org |
| Batch | url-agent batch urls.txt --concurrency 4 |
| Snapshot | url-agent snapshot https://example.com |
| Diff | url-agent diff https://example.com --snapshot snapshot.json |
| Watch | url-agent watch https://example.com --interval 300000 |
| AI reason | url-agent reason https://example.com --instruction "Summarize evidence" |
| Benchmark | url-agent benchmark |
| List actions | url-agent actions |
| Plugins | url-agent plugins |
| HTTP API | url-agent serve --host 127.0.0.1 --port 8787 |
| MCP | url-agent mcp |
| Credits | url-agent about |
Machine-oriented output:
url-agent investigate https://example.com --raw > result.jsonFull usage reference: docs/USAGE.md
URL Intelligence Agent includes a native stdio MCP server.
From source:
npm install
npm run build
npm run mcpOr after global installation:
url-agent mcp{
"mcpServers": {
"url-intelligence-agent": {
"command": "url-agent",
"args": ["mcp"],
"env": {
"URL_AGENT_MAX_PAGES": "30",
"URL_AGENT_MAX_DEPTH": "3",
"URL_AGENT_OBEY_ROBOTS": "true"
}
}
}
}If the MCP client cannot resolve your shell PATH, use an absolute Node/file path:
{
"mcpServers": {
"url-intelligence-agent": {
"command": "node",
"args": [
"/absolute/path/url-intelligence-agent/dist/src/cli.js",
"mcp"
]
}
}
}The server supports:
horno://about project/ecosystem resourceThe MCP tool registry is generated from the same core action registry used by the API.
Complete setup, tool list, JSON-RPC examples and troubleshooting:
👉 docs/MCP.md
Start locally:
url-agent serve --host 127.0.0.1 --port 8787Production authentication:
URL_AGENT_API_TOKEN=replace-with-a-long-random-token
URL_AGENT_API_RATE_LIMIT=60Health:
curl http://127.0.0.1:8787/healthInvestigate:
curl \
-H "Authorization: Bearer YOUR_TOKEN" \
-G http://127.0.0.1:8787/investigate \
--data-urlencode "url=https://example.com"Call any registered action:
curl \
-X POST \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_TOKEN" \
http://127.0.0.1:8787/action/audit_seo \
-d '{"url":"https://example.com"}'Endpoints:
GET /health
GET /actions
GET /investigate?url=...
POST /investigate
GET /action/:name
POST /action/:nameComplete API reference:
👉 docs/API.md
docker build -t url-intelligence-agent:1.0.0 .
docker run --rm \
url-intelligence-agent:1.0.0 \
investigate https://example.comdocker volume create url_agent_data
docker run -d \
--name url-intelligence-agent \
--restart unless-stopped \
--env-file .env \
-p 8787:8787 \
-v url_agent_data:/app/.url-agent \
url-intelligence-agent:1.0.0 \
serve --host 0.0.0.0 --port 8787A docker-compose.yml is included.
cp .env.example .env
docker compose up -d --buildOptional Redis service:
docker compose --profile redis up -d --buildOptional PostgreSQL service:
docker compose --profile postgres up -d --buildThe deployment guide also includes a Linux systemd service example, Nginx reverse proxy, production authentication, data persistence, renderer setup and deployment verification checklist.
The package exports the core runtime through src/index.ts.
import { investigate, runAction } from "url-intelligence-agent";
const intelligence = await investigate("https://example.com");
console.log(intelligence.entity.name.value);
console.log(intelligence.entity.name.confidence);
console.log(intelligence.entity.name.sources);
const tech = await runAction("detect_technologies", {
url: "https://example.com"
});
console.log(tech);Install as a GitHub dependency:
npm install github:vpicciuolo/url-intelligence-agentor:
{
"dependencies": {
"url-intelligence-agent": "github:vpicciuolo/url-intelligence-agent"
}
}Generate all standard report formats:
url-agent report https://example.com --out company-intelligenceOutput:
company-intelligence.md
company-intelligence.html
company-intelligence.jsonReports include project attribution and structured evidence from the investigation.
Other export workflows:
url-agent rag https://example.com
url-agent knowledge https://example.com
url-agent listing https://example.comRAG output is designed around clean, citation-friendly documents and content checksums. Knowledge output is designed around provenance-aware structured facts.
Create a snapshot:
url-agent snapshot https://example.comCompare later:
url-agent diff https://example.com --snapshot snapshot.jsonRun continuously:
url-agent watch https://example.com --interval 300000Configure webhooks:
URL_AGENT_WEBHOOK_URL=https://your-app.example/hooks/url-intelligence
URL_AGENT_WEBHOOK_SECRET=replace-with-a-secretMonitoring can surface meaningful changes between normalized intelligence snapshots instead of forcing downstream systems to compare raw HTML.
Static HTTP collection is the default.
For JavaScript-heavy pages, install Playwright:
npm install playwright
npx playwright install chromiumEnable fallback rendering:
URL_AGENT_RENDER_MODE=auto
URL_AGENT_RENDER_TIMEOUT_MS=30000Or use a compatible remote renderer:
URL_AGENT_RENDER_MODE=auto
URL_AGENT_RENDER_ENDPOINT=https://renderer.example.com/render
URL_AGENT_RENDER_API_KEY=your-keyDirect render action:
url-agent render https://example.comKeep rendering disabled when you do not need it; browser automation is significantly heavier than deterministic HTTP collection.
The main agent does not require an AI API key.
Configure an OpenAI-compatible endpoint only when reasoning is needed:
AI_BASE_URL=https://api.openai.com/v1
AI_API_KEY=
AI_MODEL=gpt-5-mini
AI_MAX_TOKENS=3000
AI_TEMPERATURE=0.1
AI_TIMEOUT_MS=30000
URL_AGENT_AI_AUTO=falseExplicit reasoning:
url-agent reason https://example.com \
--instruction "Summarize the entity and uncertainty using only supplied evidence and source URLs."The reasoning layer is instructed not to invent unsupported facts.
Start from:
cp .env.example .env| Variable | Default/example | Purpose |
|---|---|---|
URL_AGENT_TIMEOUT_MS | 10000 | Request timeout |
URL_AGENT_MAX_BYTES | 3000000 | Maximum response bytes |
URL_AGENT_MAX_REDIRECTS | 6 | Redirect bound |
URL_AGENT_MAX_PAGES | 30 | Crawl page bound |
URL_AGENT_MAX_DEPTH | 3 | Crawl depth bound |
URL_AGENT_CONCURRENCY | 4 | Crawl concurrency |
URL_AGENT_SAME_ORIGIN | true | Keep crawl same-origin |
URL_AGENT_OBEY_ROBOTS | true | Respect robots policy by default |
URL_AGENT_ALLOW_PATTERNS | empty | Optional URL allow patterns |
URL_AGENT_DENY_PATTERNS | safety defaults | URL deny patterns |
URL_AGENT_CACHE | memory | Cache adapter selection |
URL_AGENT_CACHE_TTL_MS | 300000 | Cache TTL |
URL_AGENT_CACHE_DIR | .url-agent/cache | Local cache directory |
URL_AGENT_DATA_DIR | .url-agent/data | Local persistence directory |
URL_AGENT_WORKER_CONCURRENCY | 4 | Batch worker concurrency |
URL_AGENT_RENDER_MODE | off | Render/browser mode |
URL_AGENT_RENDER_ENDPOINT | empty | Remote renderer URL |
URL_AGENT_RENDER_API_KEY | empty | Remote renderer auth |
URL_AGENT_API_TOKEN | empty | HTTP API bearer token |
URL_AGENT_API_RATE_LIMIT | 60 | Requests/client/minute |
URL_AGENT_CORS_ORIGIN | empty | Optional API CORS origin |
URL_AGENT_WEBHOOK_URL | empty | Monitoring webhook |
URL_AGENT_WEBHOOK_SECRET | empty | Webhook signing/auth secret |
REDIS_URL | empty | Optional Redis connection |
VALKEY_URL | empty | Optional Valkey connection |
DATABASE_URL | empty | Optional PostgreSQL connection |
AI_BASE_URL | OpenAI-compatible | Optional model endpoint |
AI_API_KEY | empty | Optional model API key |
AI_MODEL | gpt-5-mini | Optional model name |
URL_AGENT_AI_AUTO | false | Automatic AI reasoning toggle |
The default settings intentionally bound network and crawl behavior. Increase them only when your workload requires it.
Every submitted URL is treated as untrusted input.
The network layer includes protections such as:
The crawler is designed for public web intelligence. It does not intentionally bypass authentication, CAPTCHAs or access controls.
Security/trust scores are public signal summaries — not penetration tests, legal opinions, fraud determinations or guarantees of security.
See SECURITY.md.
The codebase is intentionally modular:
src/
├── agent.ts orchestration + action registry
├── net.ts URL safety / fetching / probing
├── crawler.ts robots / sitemap / bounded crawling
├── extract.ts deterministic page extraction
├── render.ts Playwright / remote render adapters
├── domain.ts DNS / mail / TLS intelligence
├── analyzers.ts SEO / security / quality / trust / tech / brand
├── extensions.ts API / commerce / people / links / knowledge
├── monitor.ts snapshots / diff / webhook
├── watch.ts continuous monitoring
├── adapters.ts cache / persistence / worker adapters
├── ai.ts optional OpenAI-compatible reasoning
├── plugins.ts plugin SDK/runtime
├── report.ts terminal / Markdown / HTML reports
├── server.ts HTTP API
├── mcp.ts MCP stdio server
├── benchmark.ts reliability benchmark runner
└── cli.ts interactive + command-line experienceMore detail: docs/ARCHITECTURE.md
| Guide | Use it when... |
|---|---|
| Complete Usage Guide | You want every main command, recipe and integration example |
| MCP Guide | You want to connect the agent to an MCP-compatible AI client |
| Deployment Guide | You want Docker, Compose, systemd, Nginx or production API deployment |
| HTTP API Guide | You want endpoint, auth, curl, JS and Python examples |
| Action Reference | You want the runtime action catalog |
| Architecture | You want to understand internal modules and design |
| Security | You want the public-URL/network safety model |
| Contributing | You want to improve the project |
URL Intelligence Agent is designed for applications such as:
The listing-generation and URL enrichment workflows are especially useful when a user pastes a URL and your product needs to turn it into an editable, evidence-backed profile instead of asking the user to fill every field manually.
Typecheck:
npm run typecheckTests:
npm testBenchmark:
npm run benchmarkThe repository includes a benchmark fixture under benchmarks/urls.json for repeatable reliability testing.
Contributions are welcome, particularly around:
Please read CONTRIBUTING.md before submitting substantial changes.
If URL Intelligence Agent saves you engineering time, becomes part of your product, or you simply want to support more open-source tools from this ecosystem, you can support the work here:
Support page: https://hrn.ae/githubsupport
GitHub README files cannot safely execute Stripe JavaScript widgets, so the button links directly to the dedicated Stripe-enabled support page.
Created by Vincenzo Picciuolo
Founder & Lead Engineer — HRN Innovation Technologies Ltd
Built as part of the technology work behind the HORNO ecosystem and released openly for developers and builders.
If you use the project, ⭐ star the repository, open an issue with feedback, or show us what you build with it.
MIT © 2026 HRN Innovation Technologies Ltd — Vincenzo Picciuolo.
Pick your client and paste the snippet. Each one is the same server, written the way that client expects it.
claude mcp add url-intelligence-agent -- url-agent mcp{
"mcpServers": {
"url-intelligence-agent": {
"env": {
"URL_AGENT_MAX_DEPTH": "",
"URL_AGENT_MAX_PAGES": "",
"URL_AGENT_OBEY_ROBOTS": ""
},
"args": [
"mcp"
],
"command": "url-agent"
}
}
}code --add-mcp '{"name":"url-intelligence-agent","env":{"URL_AGENT_MAX_DEPTH":"","URL_AGENT_MAX_PAGES":"","URL_AGENT_OBEY_ROBOTS":""},"args":["mcp"],"command":"url-agent"}'[mcp_servers.url-intelligence-agent]
command = "url-agent"
args = ["mcp"]Runs locally on your device. Your client starts the server itself, so nothing has to be hosted.
Paste this prompt into your agent. It reads this page and does the setup for you.
Read https://aiagentslisting.com/mcp/url-intelligence-agent to learn what the "Url Intelligence Agent" MCP server does and how to install it. Add it to my coding agent's MCP configuration as documented on that page, then confirm the server connects and list the tools it exposes.Agents can also browse this directory over MCP at https://aiagentslisting.com/api/mcp
docker run --rm
docker run -dnpx playwright install chromiumThis server runs locally, so we can't read its tool list over the web yet.
A powerful Model Context Protocol (MCP) server that provides an all-in-one solution for public web a
Your SEO and AI Visibility Growth Engine. Verified SEO Scores. Open SEO Playbook. Public SEO Proof.
The Apify MCP server enables your AI agents to extract data from social media, search engines, maps,
v1.0.0URL Intelligence Agent v1.0.0 — Unified Intelligence ReleaseRelease notesConnect to the AI Agents Listing MCP server at https://aiagentslisting.com/api/mcp using the HTTP transport and complete the sign-in when it asks. Then call the submit_review tool for the listing "url-intelligence-agent" with a rating from 1 to 5 and a short note on what worked and what did not.No reviews yet
Be the first to share your experience with this tool.
A powerful Model Context Protocol (MCP) server that provides an all-in-one solution for public web a
Browser & Scraping
Your SEO and AI Visibility Growth Engine. Verified SEO Scores. Open SEO Playbook. Public SEO Proof.
AI & ML Services
The Apify MCP server enables your AI agents to extract data from social media, search engines, maps,
Browser & Scraping
One email a week. New agents, MCP servers and skills, and what is actually getting traction.