by fabien-desablens
Webpage Timestamps extracts and consolidates creation, modification, and publication dates from web pages for accurate f
Extracts when web pages were created, modified, or published by analyzing HTML metadata, headers, and structured data. Returns timestamps with confidence scores to help you understand content freshness and publication dates.
Webpage Timestamps is a community-built MCP server published by fabien-desablens that provides AI assistants with tools and capabilities via the Model Context Protocol. Webpage Timestamps extracts and consolidates creation, modification, and publication dates from web pages for accurate f It is categorized under search web, analytics data. This server exposes 2 tools that AI clients can invoke during conversations and coding sessions.
You can install Webpage Timestamps in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
Webpage Timestamps is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Fetch and extract information from websites automatically
Example
Research competitor pricing, scrape product reviews, monitor news mentions
Automate 5-10 hours/week of manual web research
Track website changes, new content, price updates
Example
Monitor competitor blog for new posts, track stock availability, watch for pricing changes
Stay informed without manual checking, never miss important updates
Extract structured data from multiple websites
Example
Compile product listings from 10 e-commerce sites, aggregate job postings, collect real estate data
Build datasets 100x faster than manual copying
Share your MCP server with the developer community
I recommend Webpage Timestamps for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
We wired Webpage Timestamps into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Webpage Timestamps is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Useful MCP listing: Webpage Timestamps is the kind of server we cite when onboarding engineers to host + tool permissions.
Strong directory entry: Webpage Timestamps surfaces stars and publisher context so we could sanity-check maintenance before adopting.
I recommend Webpage Timestamps for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Strong directory entry: Webpage Timestamps surfaces stars and publisher context so we could sanity-check maintenance before adopting.
According to our notes, Webpage Timestamps benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
Useful MCP listing: Webpage Timestamps is the kind of server we cite when onboarding engineers to host + tool permissions.
Webpage Timestamps is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
showing 1-10 of 41
A powerful Model Context Protocol (MCP) server for extracting webpage creation, modification, and publication timestamps. This tool is designed for web scraping and temporal analysis of web content.
npm install -g mcp-webpage-timestamps
npx mcp-webpage-timestamps
To install mcp-webpage-timestamps for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @Fabien-desablens/mcp-webpage-timestamps --client claude
git clone https://github.com/Fabien-desablens/mcp-webpage-timestamps.git
cd mcp-webpage-timestamps
npm install
npm run build
The server can be used with any MCP-compatible client. Here's how to configure it:
Add to your claude_desktop_config.json:
{
"mcpServers": {
"webpage-timestamps": {
"command": "npx",
"args": ["mcp-webpage-timestamps"],
"env": {}
}
}
}
Add to your MCP settings:
{
"mcpServers": {
"webpage-timestamps": {
"command": "npx",
"args": ["mcp-webpage-timestamps"]
}
}
}
# Start the server
npm start
# Or run in development mode
npm run dev
extract_timestampsExtract timestamps from a single webpage.
Parameters:
url (string, required): The URL of the webpage to extract timestamps fromconfig (object, optional): Configuration optionsConfiguration Options:
timeout (number): Request timeout in milliseconds (default: 10000)userAgent (string): User agent string for requestsfollowRedirects (boolean): Whether to follow HTTP redirects (default: true)maxRedirects (number): Maximum number of redirects to follow (default: 5)enableHeuristics (boolean): Enable heuristic timestamp detection (default: true)Example:
{
"name": "extract_timestamps",
"arguments": {
"url": "https://example.com/article",
"config": {
"timeout": 15000,
"enableHeuristics": true
}
}
}
batch_extract_timestampsExtract timestamps from multiple webpages in batch.
Parameters:
urls (array of strings, required): Array of URLs to extract timestamps fromconfig (object, optional): Same configuration options as extract_timestampsExample:
{
"name": "batch_extract_timestamps",
"arguments": {
"urls": [
"https://example.com/article1",
"https://example.com/article2",
"https://example.com/article3"
],
"config": {
"timeout": 10000
}
}
}
Both tools return a JSON object with the following structure:
{
url: string;
createdAt?: Date;
modifiedAt?: Date;
publishedAt?: Date;
sources: TimestampSource[];
confidence: 'high' | 'medium' | 'low';
errors?: string[];
}
TimestampSource:
{
type: 'html-meta' | 'http-header' | 'json-ld' | 'microdata' | 'opengraph' | 'twitter' | 'heuristic';
field: string;
value: string;
confidence: 'high' | 'medium' | 'low';
}
article:published_timearticle:modified_timedatepubdatepublishdatelast-modifieddc.date.createddc.date.modifieddcterms.createddcterms.modifiedLast-ModifiedDatedatePublisheddateModifieddateCreateddatePublisheddateModifiedog:article:published_timeog:article:modified_timeog:updated_timetwitter:data1 (when containing date information)datetime attributes# Development with hot reload
npm run dev
# Build the project
npm run build
# Run tests
npm test
# Run tests in watch mode
npm run test:watch
# Lint code
npm run lint
# Fix linting issues
npm run lint:fix
# Format code
npm run format
The project includes comprehensive tests:
# Run all tests
npm test
# Run tests with coverage
npm test -- --coverage
# Run specific test file
npm test -- extractor.test.ts
import { TimestampExtractor } from './src/extractor.js';
const extractor = new TimestampExtractor();
const result = await extractor.extractTimestamps('https://example.com/article');
console.log('Published:', result.publishedAt);
console.log('Modified:', result.modifiedAt);
console.log('Confidence:', result.confidence);
console.log('Sources:', result.sources.length);
const extractor = new TimestampExtractor({
timeout: 15000,
userAgent: 'MyBot/1.0',
enableHeuristics: false,
maxRedirects: 3
});
const result = await extractor.extractTimestamps('https://example.com');
const urls = [
'https://example.com/article1',
'https://example.com/article2',
'https://example.com/article3'
];
const results = await Promise.all(
urls.map(url => extractor.extractTimestamps(url))
);
The extractor handles various error conditions gracefully:
All errors are captured in the errors array of the response, allowing for robust error handling and debugging.
We welcome contributions! Please see our Contributing Guide for details.
git clone https://github.com/Fabien-desablens/mcp-webpage-timestamps.gitnpm installgit checkout -b feature/your-featurenpm testgit commit -m 'Add some feature'git push origin feature/your-featureMIT License - see the LICENSE file for details.
See CHANGELOG.md for a detailed history of changes.
Interact with services that don't offer APIs
Example
Check form submissions, validate website functionality, test user flows
Automate interactions with any website, even without API
Prerequisites
Time Estimate
20-40 minutes including configuration and testing
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
MCP server handles HTTP requests, HTML parsing, JavaScript rendering (if headless browser), and returns structured data to Claude.
Protocols
Compatibility
✓ Use when
Use for research automation, content monitoring, data aggregation from multiple sources, and when official APIs don't exist. Best for read-only information gathering.
✗ Avoid when
Avoid for sites with APIs (use API instead), sites that explicitly forbid scraping, when data is copyrighted, or for login-required content without proper authorization.